EOF moves forward despite dev friction
It is a section from the 0xResearch publication. To learn full editions, subscribe.
On Thursday’s ACD name, Ethereum core builders reaffirmed their intent to ship Full EOF (EVM object format) with the Fusaka fork alongside the PeerDAS principal driver. (Ipsilon wrote up a radical assessment of the choices, with Full EOF known as “Possibility A.”)
EOF is a significant overhaul of the EVM that goals for long-term optimization, security and modularity of Ethereum’s execution engine.
Its scope has stirred controversy. Felix (from the Geth group) backed the extra average Possibility D, placing him barely at odds with fellow Geth school Lightclients.
From exterior the shopper groups, Pascal Caversaccio voiced robust opposition, following up on his printed critique: “EOF: When Complexity Outweighs Necessity.” His principal declare: No software builders are asking for EOF, and its rollout dangers alienating the broader dev neighborhood.
Regardless of this, EF workers — together with Piper Merriam and Ansgar Dietrichs, in addition to shopper groups like Besu and Erigon — stood behind Full EOF. Their reasoning: It’s a clear structural reset, demanded by compiler authors, and backward-compatible for builders preferring the legacy EVM.
