Test case: initcode-mode not being EOF-validated #855
Merged
+24
−0
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.
Recently on the EOF impl call we discussed a potential rule to validate and prohibit "weird" mixing of initcode-mode being on or off - during EOF validation.
We concluded we do not find such validation rule useful enough. In case this rule withstands the test of time, we should have a test case for this.
I think this is a test case where we acertain, that none of the following conditions are validated:
This quote is taken from the potential addition to the rationale section of EIP-7620, as PRed here: https://github.com/ethereum/EIPs/blob/d8149857a036b69f24c9f8d56fa87dbd0bbf2d0c/EIPS/eip-7620.md#eof-validation-checking-initcode-mode