This is a segment from the 0xResearch newsletter. To read full editions, subscribe.
During Thursday’s ACD call, Ethereum core developers confirmed their plans to implement Full EOF (EVM object format) with the Fusaka fork alongside the PeerDAS main driver. (Ipsilon provided a detailed analysis of the options, with Full EOF being referred to as “Option A.”)
EOF represents a significant overhaul of the EVM, focusing on long-term optimization, safety, and modularity of Ethereum’s execution engine.
However, the scope of EOF has sparked debate within the community. Felix, from the Geth team, supported the more moderate Option D, which slightly diverged from the stance of his fellow Geth colleagues in the Lightclients team.
External to the client teams, Pascal Caversaccio expressed strong opposition, echoing his published criticism in “EOF: When Complexity Outweighs Necessity.” His primary argument is that no application developers have requested EOF, and its implementation may risk alienating the broader developer community.
Despite the dissenting opinions, EF staff — including Piper Merriam and Ansgar Dietrichs — as well as client teams like Besu and Erigon, remained in favor of Full EOF. Their rationale is that it offers a clean structural reset, as demanded by compiler authors, while remaining backward-compatible for developers who prefer the legacy EVM.