-
Notifications
You must be signed in to change notification settings - Fork 545
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
Ethereum hardfork: Cancun #527
Comments
@Evalir regarding this q: foundry-rs/foundry#5574 (comment) ETA depends on Ethereum core devs and when they finalise Cancun, for example, EIP-4788 got a major change last week. I decided to drop #536 PR as i need to be mindful of my time and it is safer to just rewrite it, as I got burned with mcopy that took a lot of my time, and in the end, there were multiple consensus issues found after it was merged #528, if you want you can take a stab at it on rewriting it, be free to do it. Others EIP I would not recommend,as beaconroot is not finished and selfdestruct requires a lot of local knowledge. |
@rakita makes sense—thanks for the update! I think I might leave 4844 up to you—it's true that it's quite sensitive to get right as a bug here affects reth upstream, and I'm not as familiar with the EIP as a whole, nor any upstream assumptions we might have from reth. For now foundry is on latest main and unblocked the sol team, so it should be good for now for 1153 👍 |
This can be closed @rakita |
Implemented and released inside revm |
List of EIP for Cancun upgrade:
Execution spec
The text was updated successfully, but these errors were encountered: