-
Notifications
You must be signed in to change notification settings - Fork 75
[ETCM-921] transaction with access list #1094
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
strauss-m
merged 13 commits into
develop
from
feature/etcm-921_transaction_with_access_list
Aug 23, 2021
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
538468f
[ETCM-911] Replace LegacyTX with trait Transaction in SignedTransaction
dzajkowski f94fd19
[ETCM-911] Drop unused 'chainId' parameter from constructor
dzajkowski 01ea9c4
[ETCM-911] Add rlp serialization basics
dzajkowski ce79889
[ETCM-911] Add rlp tests showing compatibility with geth
dzajkowski 68e4ef0
[ETCM-921] rlp access list encoding + unit tests
strauss-m 200c70b
[ETCM-921] formatting + code review changes
strauss-m f312382
[ETCM-921] code review feedback
strauss-m a47b4c6
[ETCM-921] read chainId from rlp transaction instead of config
strauss-m c18072e
[ETCM-921] rlp encoding and decoding test for Seq[SignedTransaction]
strauss-m 05fe3dc
[ETCM-921] Introduce PrefixedRLPEncodable to handle binary prefixed R…
strauss-m 1f8bb2d
[ETCM-921] properly decode SignedTransaction in BlockBody + scaladoc
strauss-m eac11af
[ETCM-921] Clean magic number and add unit test for PrefixedRLPEncodable
strauss-m c52e95a
[ETCM-921] Code review feedback changes
strauss-m File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isn't this up to 0xFF?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
0x7f is the limit for two reasons:
That's what allows us to consider a single RLPValue [0; 0x7f] as a single raw byte transaction type (and vice-versa)
Since Byte is a signed type, the range [0; 0x7f] check become a simple positive condition.