-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
EIP 3540 Addition: EOF1 contracts can only DELEGATECALL EOF1 contracts #6359
Conversation
As suggested by Paweł Bylica (@chfast) I am proposing this EIP addition.
File
|
The commit cd1bf3c (as a parent of 05487be) contains errors. |
Added Test Cases
As discussed on Discord, no restrictions are being placed on any of the following DELEGATECALLs: - EOF2 -> EOF1 - EOF1 -> EOF2 These are left for future consideration.
Co-authored-by: Paweł Bylica <[email protected]>
The code targeted by DELEGATECALL from an EOF must also be an EOF. This restriction has been added to EIP-3540 in ethereum/EIPs#6359.
According to EIP-3540 updated by ethereum/EIPs#6359 a DELEGATECALL from EOF to legacy code is disallowed. This updates expectations in the single test case of DELEGATECALL EOF → legacy.
The code targeted by DELEGATECALL from an EOF must also be an EOF. This restriction has been added to EIP-3540 in ethereum/EIPs#6359.
According to EIP-3540 updated by ethereum/EIPs#6359 a DELEGATECALL from EOF to legacy code is disallowed. This updates expectations in the single test case of DELEGATECALL EOF → legacy.
The code targeted by DELEGATECALL from an EOF must also be an EOF. This restriction has been added to EIP-3540 in ethereum/EIPs#6359.
According to EIP-3540 updated by ethereum/EIPs#6359 a DELEGATECALL from EOF to legacy code is disallowed. This updates expectations in the single test case of DELEGATECALL EOF → legacy.
According to EIP-3540 updated by ethereum/EIPs#6359 a DELEGATECALL from EOF to legacy code is disallowed. This updates expectations in the single test case of DELEGATECALL EOF → legacy.
There has been no activity on this pull request for 2 weeks. It will be closed after 3 months of inactivity. If you would like to move this PR forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review. |
This pull request was closed due to inactivity. If you are still pursuing it, feel free to reopen it and respond to any feedback or request a review in a comment. |
As suggested by Paweł Bylica (@chfast) I am proposing this EIP addition.
Full discussion here: https://ethereum-magicians.org/t/evm-object-format-eof/5727/48