This is a segment of the 0xresearch newsletter. Subscribe to read full editions.
At the ACD call on Thursday, Ethereum -Kerneelpoerters confirmed their intention to send Full EOF (EVM Object -format) with the Fusaka Fork next to the main driver of Peerdas. (Ipsilon wrote a thorough assessment of the options, referred to as “option A.”)
EOF is an important overhaul of the EVM that strives for optimization in the long term, safety and modularity of the Ethereum implementing engine.
The scope has stirred controversy. Felix (from the GEth team) supported the more moderate option D, which made him somewhat at odds with colleague Geth College Light clients.
Pascal Caversaccio expressed strong opposition from outside the customer teams and followed his published criticism: “EOF: When complexity weighs the need more heavily.” His most important claim: do not ask for application developers for EOF and the rollout risks to alienate the wider DEV community.
Nevertheless, EF employees – including Piper Merriam and Ansgar Dietrichs, as well as customer teams such as Besu and Erigon – supported the entire EOF. Their reasoning: it is a clean structural reset, demanded by compiler authors, and backward compatible for developers who prefer the Legacy EVM.