-
Notifications
You must be signed in to change notification settings - Fork 356
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 include EIP-3541 in London #307
Comments
We agreed on ACD 112 to move EIP-3541 to CFI and decide about London inclusion on the following call. It's been updated in the tracker board. |
The draft has been merged (https://eips.ethereum.org/EIPS/eip-3541) and comprehensive tests are in a PR to ethereum/tests (ethereum/tests#835). |
Thanks, @axic. Added the proper commit in the Baikal spec. |
Thanks! Could you also change the link on the left hand side? It still points to the PR. |
Good catch, done 👍 |
@timbeiko we have pushed unit tests into the EIP and the status was also updated to review. Perhaps you want to change the commit hash to include the tests, but the comprehensive test changes are in ethereum/tests#835 anyway. |
Updated in the baikal spec, @axic 👍 |
Closing given we agreed to include this in London in #309 |
We propose to include EIP-3541 in London (it is only an EIP PR right now, but hopefully gets merged in a few days).
This change is very simple itself and is the first step of the larger EIP-3540, which we hope to have included in Shanghai.
It is important to consider 3541 for London, otherwise 3540 would be delayed to Cancun at earliest. We think including 3541 will not cause any delay to London, given its simplicity.
The text was updated successfully, but these errors were encountered: