EOF removed from Fusaka upgrade (Declined for Inclusion)
[Reasoning by @timbeiko copied from Update EIP-7607: Remove EOF from Fusaka by timbeiko · Pull Request #9703 · ethereum/EIPs · GitHub]
Reasoning
On “ACDT” 34, a decision was made to remove EOF from Fusaka.
The process here was highly unusual. I encourage people to listen to the full discussion. Here are the reasons why I think this is the correct outcome, despite several client teams expressing support for EOF:
- Risks to Fusaka timelines: all client teams, ELs included, seem to agree that shipping PeerDAS ASAP is Ethereum’s most important priority. While this wasn’t a major topic of discussion on the call, it’s worth acknowledging that debating variants of the EOF spec at this point affects our ability to ship. As we move towards Fusaka devnets, and coupling EL & CL changes, keeping EOF would increasingly become the default path. While there are ways to mitigate this risk, such as the modular EOF devnets proposed by the EIPs’ champions, it is nevertheless a risk, and one we should only take if we feel the payoff is significant. Points (2) and (3) below make me question this.
- Technical uncertainty about impact: while there seemed to be broad support on the call towards the Option D variant, midway through, some participants realized that they did not understand the implications of this variant. Reasoning about the implications of an EIP’s semantic change should ideally happen much earlier in the process. Had another EIP with similar levels of open questions been proposed on today’s call, ACD would have rejected it without hesitation.
- Process considerations: last but not least, I think the entire EOF inclusion debate has shown failures in ACD’s prioritization process. While core devs originally agreed to ship EOF (many times), at each occasion, many prominent community members raised objections to it. While, individually considered, it didn’t seem like any of these concerns warranted EOF’s removal, zooming out, it’s clear that ACD’s feedback loops failed at addressing these concerns.
Given the above, and the intention to reconfigure AllCoreDevs for Glamsterdam, it seems right to remove EOF from Fusaka while leaving the door for its champions to present a case for it in Glamsterdam, where hopefully the process begins by assessing what the highest impact changes for Ethereum as a whole are.
My apologies to everyone who has sunk more time into this than they should have because of the process failures. I hope we can learn from this to improve how we plan upgrades going forward 
Summary
[Summary by @poojaranjan copied from Interop Testing #34 | April 28 2025 · Issue #1499 · ethereum/pm · GitHub]
- Mainnet Shadow Fork in progress; EF Testing prepping a new BLS-heavy test release.
- PeerDAS Devnet 6 deprecated; Devnet 7 coming this week.
- Consensus spec update PR (#4291) proposed to align EL and CL minimal specs.
- EOF Discussion: After strong debate, EOF removed from Fusaka upgrade.
- Option D explored (limited introspection), but community support was split.
- Focus shifted back to PeerDAS + scaling improvements for Fusaka.
- App dev feedback emphasized — stronger app-dev engagement required for future EVM upgrades.
- Future EOF considerations deferred to Glamsterdam cycle.
Notes & chat log
Recordings
https://www.youtube.com/live/M3DWaWbIB3s?t=53s
https://x.com/EthCatHerders/status/1916854796692390082
Additional info
1 Like