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.

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

Proposal to add EIP-2315 (Simple Subroutines) and EIP-4200 (Static Relative Jumps) into Shanghai. #469

Closed
gcolvin opened this issue Feb 2, 2022 · 2 comments

Comments

@gcolvin
Copy link

gcolvin commented Feb 2, 2022

This is an early indication to seek inclusion of EIP-2315 (Simple Subroutines) and EIP-4200 (Safer Control Flow) into Shanghai.

@gcolvin gcolvin changed the title Proposal to add EIP-2315 (Simple Subroutines) into Shanghai. Proposal to add EIP-2315 (Simple Subroutines) and EIP-3379 (Safer Control Flow) into Shanghai. Feb 2, 2022
@gcolvin gcolvin changed the title Proposal to add EIP-2315 (Simple Subroutines) and EIP-3379 (Safer Control Flow) into Shanghai. Proposal to add EIP-2315 (Simple Subroutines) and EIP-3779 (Safer Control Flow) into Shanghai. Feb 2, 2022
@gcolvin
Copy link
Author

gcolvin commented Sep 14, 2022

EIP-2315 remains substantially the same since 2017 -- one opcode to jump to a subroutine and one to return. Thanks to the Ethereum Object Format it now takes its arguments as static immediate data. It deprecates JUMP and JUMPI and together with Code Validation and Static Relative Jumps it ensures, at initialization time, that valid code will not execute invalid instructions or jump to invalid locations, will not underflow stack, will maintain consistent numbers of inputs and outputs for subroutines, and will have bounded stack height in the absence of recursion.

@gcolvin gcolvin changed the title Proposal to add EIP-2315 (Simple Subroutines) and EIP-3779 (Safer Control Flow) into Shanghai. Proposal to add EIP-2315 (Simple Subroutines) and EIP-4200 (Static Relative Jumps) into Shanghai. Sep 14, 2022
@timbeiko
Copy link
Collaborator

Closing this issue as the EOF is now a candidate replacement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants