Skip to content
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.

Sign up for GitHub

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

Update EIP-2315: Catch up to latest Yellow Paper #5814

Merged
merged 3 commits into from
Oct 23, 2022
Merged

Update EIP-2315: Catch up to latest Yellow Paper #5814

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
50e8423
Catch up to latest Yellow Paper
gcolvin Oct 22, 2022
8401311
Merge branch 'master' into patch-1
Pandapip1 Oct 23, 2022
5b90e9a
Remove yellow paper ref so that PR can be merged
Pandapip1 Oct 23, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion EIPS/eip-2315.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,7 +96,7 @@ _Execution_ is defined in the Yellow Paper as sequence of changes in the EVM sta
5. Invalid jump destination
6. Invalid instruction

We would like to consider EVM code valid iff no execution of the program can lead to an exceptional halting state. In practice, we must test at runtime for conditions 1, 2, and 3 — sufficient gas, sufficient stack, and modification of static state. We don’t know how much gas there will be, we don’t know how deep a recursion may go, analysis of stack depth even for non-recursive programs is nontrivial, and we don't know whether a call will be static. All of the remaining conditions MUST be validated statically, in time and space quasi-linear in the size of the code.
We would like to consider EVM code valid iff no execution of the program can lead to an exceptional halting state. In practice, we must test at runtime for conditions 1, 2, and 3 — sufficient gas and sufficient stack. We don’t know how much gas there will be, we don’t know how deep a recursion may go, analysis of stack depth even for non-recursive programs is nontrivial, and we don't know whether a call will be static. All of the remaining conditions MUST be validated statically, in time and space quasi-linear in the size of the code.

#### Static Constraints on Valid Code

Expand Down