9.4.3. Jump Destination Validity - be explicit about validation#842
Open
loredanacirstea wants to merge 1 commit intoethereum:masterfrom
Open
9.4.3. Jump Destination Validity - be explicit about validation#842loredanacirstea wants to merge 1 commit intoethereum:masterfrom
loredanacirstea wants to merge 1 commit intoethereum:masterfrom
Conversation
The sentence "must appear within the explicitly defined portion of the code" leads the reader to think that only executable code is checked for JUMPDEST validity. In practice, all clients validate jump destinations prior to execution.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The sentence "must appear within the explicitly defined portion of the code"
leads the reader to think that only executable code is checked for JUMPDEST validity.
In practice, all clients validate jump destinations prior to execution.
The problem was detailed in #840.