Set execution params to presets #2702
Merged
Conversation
This file contains 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
|
Second thought: the assertion would be incorrect if minimal preset value is different from the mainnet preset value. I can revert it if they are likely to be changed. |
ralexstokes
reviewed
Nov 1, 2021
| @@ -64,7 +63,7 @@ Additionally, this upgrade introduces the following minor changes: | |||
| | `Transaction` | `ByteList[MAX_BYTES_PER_TRANSACTION]` | either a [typed transaction envelope](https://eips.ethereum.org/EIPS/eip-2718#opaque-byte-array-rather-than-an-rlp-array) or a legacy transaction| | |||
| | `ExecutionAddress` | `Bytes20` | Address of account on the execution layer | | |||
|
|
|||
| ## Constants | |||
| ## Preset | |||
hwwhww
changed the title
|
@ralexstokes Thanks for the review! I reverted the |
ralexstokes
approved these changes
Nov 2, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Spec builder fixes:
Add spec builder assertions to avoid Update max transaction size in setup.py #2701 issue happening againIt will addassert MAX_BYTES_PER_TRANSACTION == uint64(1073741824)to the spec.