Key Takeaways:
- Fusaka upgrade targets Q3–Q4 2025 but without the EVM Object Format (EOF).
- Developers cited technical uncertainty and timeline risks for dropping EOF.
- Focus shifts to PeerDAS priority as Ethereum plans for smoother future upgrades.
Ethereum’s road to its next significant network evolution, Fusaka, is being increasingly shaped by critical decisions being made by its community. Coming in the third or fourth quarter of 2025, Fusaka is being billed as an important next step.
But the EVM Object Format, originally slated for inclusion in this upgrade, will also no longer be part of it. The announcement was made during ACDT 34 by key players like Tim Beiko and Tomasz Kajetan Stańczak, after thorough community discussions and technical evaluations.
EOF was initially introduced to make smart contract execution more efficient, enhancing efficiency through bytecode structure standardization in Ethereum. Despite its advantages, risks associated with its deployment that might have slowed down the entire Fusaka deployment were cited by developers.
In an April 28 post on X, Tomasz Kajetan Stańczak clarified that ongoing discussions about EOF are separate from the imminent Pectra upgrade, set for May 7th, which remains unaffected and on schedule. Stańczak emphasized that EOF debates only concern the later Fusaka phase.
Developer Consensus Leans Toward Stability
Beiko summarized in a GitHub post that although there was overall initial consensus across Ethereum’s implementation teams behind EOF, further analysis demonstrated significant uncertainties from a technical perspective.
Some of the participants late in discussions on the call accepted that they hadn’t comprehended the long-term consequences of EOF’s Option D variant.
This was a concern about how major protocol change evaluation was being conducted overall. Beiko identified that proposals that were uncertain in terms of technical impact would, in more normal circumstances, have been rejected straightaway.
Emphasizing threats to the Fusaka timelines, Beiko underscored that shipping PeerDAS, a novel data availability offering, should be the top priority of the ecosystem.
The risks of potential delays through final touches or misconceptions about EOF made removing it the most reasonable choice.
Lessons for Future Ethereum Upgrades
The EOF debate revealed more fundamental issues with Ethereum’s upgrade decision-making process. The fact that EOF was repeatedly approved in light of persistent issues indicated more fundamental failures in AllCoreDev’s feedback loops.
Instead of forging ahead into uncertain change, an agreement was made by developers that it would be advisable to fix these systemic problems before making future upgrades.
Removing EOF doesn’t signify its end of prospects, as its proponents would still be able to present a better version to be upgraded further later, such as Glamsterdam.
The main takeaway from Fusaka preparations is evident: Ethereum’s early-stage governance needs stronger scrutiny and more disciplined prioritization to avoid eleventh-hour course corrections.
By giving a higher priority to stability and diverting resources to PeerDAS, Ethereum core developers are hoping to make sure that the network upgrades smoothly without delays, creating a stronger base for future years.
Related Reading | UAE to Launch Dirham-Backed Stablecoin to Boost Digital Payments