This is a segment of the 0xResearch newsletter. Subscribe to read the full edition.
On Thursday’s ACD call, the Ethereum Core developers reaffirmed their intention to ship full EOF (EVM object format) using Fusaka Fork along with Peerdas’ main driver. (Epsilon wrote a thorough review of options. The complete EOF is called “Option A”)
EOF is a major overhaul of EVMs aimed at long-term optimization, safety and modularity of Ethereum’s execution engine.
The scope has sparked controversy. Felix (of Geth Team) favored a more moderate option D, and was in a slight conflict with fellow Geth College Lightclients.
From outside the client team, Pascal Cauccio expressed strong opposition, following his published critiques, “EOF: When Complexity Overcomes Need.” His main argument: Because application developers do not want EOF, their deployment risk marginalizes the wider development community.
Nevertheless, EF staff, including client teams like Piper Merriam and Ansgar Dietrichs, as well as Besu and Erigon, stood behind the full EOF. Their reasoning: It’s a clean structure reset requested by the compiler authors, and is backwards compatible for developers who prefer legacy EVMs.
