This is a segment from the 0xResearch newsletter. To read full editions, subscribe.
Ethereum Core Developers Plan to Implement Full EOF with Fusaka Fork
During Thursday’s ACD call, Ethereum core developers confirmed their decision to include Full EOF (EVM object format) in the Fusaka fork alongside the PeerDAS main driver. This move, also known as “Option A,” was discussed in detail by Ipsilon in a recent review.
The Significance of EOF in Ethereum
EOF represents a significant overhaul of the EVM, focusing on enhancing long-term optimization, safety, and modularity of Ethereum’s execution engine.
However, the scope of EOF has sparked some debate within the community. Felix, a member of the Geth team, expressed support for the more moderate Option D, leading to a slight divergence of opinions within the Geth team itself.
External voices, such as Pascal Caversaccio, have also raised concerns about EOF. Caversaccio’s critique, titled “EOF: When Complexity Outweighs Necessity,” argues that EOF is not a priority for application developers and could potentially alienate the broader development community.
Support for Full EOF
Despite the criticism, key figures within the Ethereum Foundation, including Piper Merriam and Ansgar Dietrichs, as well as client teams like Besu and Erigon, continue to advocate for Full EOF. They believe that it offers a clean structural reset, addresses the needs of compiler authors, and maintains backward compatibility for developers who prefer the legacy EVM.