Fusaka will become the next Ethereum upgrade without Ethereum Object Format (EOF), especially after the developer responds to community resistance. On April 28, during the Ethereum All Core Developers call, stakeholders validated the removal of the EOF by mentioning its uncertain technical complexity.
The Ethereum development community established EOF as a collection of EIPs that sought to enhance brilliant contract creation while making development more expedient and transparent. The Ethereum Foundation removed EOF from Fusaka to eliminate development delays because the intended integration into the future version was unfitting.
According to Tim Beiko, Protocol Support Lead at the Ethereum Foundation, client teams opted to remove EOF to focus on a more urgent feature. The upgrade will now prioritize PeerDAS, a data availability solution expected to enhance Ethereum’s scalability and performance.
Developer opposition strengthened significantly after Tomasz Stańczak from the Ethereum Foundation signaled that EOF would appear in Fusaka during a recent announcement. The introduction of EOF suffered from implementation uncertainty and readiness questions, which divided the community members.
The coordination process became difficult because of the multiple versions of EOF, which prompted debate, according to Beiko. According to his assessment, the developers showed insufficient understanding about the proposed variant, which made the upgrade process more intricate.
A lack of shared perspective and unclear information exchanged during past sessions resulted in the chosen outcome. The decision to focus on PeerDAS provides better support for present development priorities while speeding up the delivery of essential components for Fusaka.
Most developers accepted that eliminating EOF from the next upgrade does not stop the possibility of including EOF in future versions. Supporters of the proposal could consider EOF during future Glamsterdam development planning once all parties unite in their direction.
Additional waiting time represents an opportunity for the Ethereum Foundation to reorganize proposal schedules to prevent recurring coordination challenges. The decision represents a significant development for Ethereum because it allows the community to steer future technical directions.
Conclusion
The removal of EOF from Fusaka reflects a shift in Ethereum’s upgrade strategy toward more immediate and widely supported features. Development teams will now concentrate on PeerDAS as they prepare for the next phase of Ethereum’s scaling roadmap.
