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 major driver. (Ipsilon wrote up an intensive evaluate 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 workforce) backed the extra average Possibility D, placing him barely at odds with fellow Geth faculty Lightclients.
From exterior the consumer groups, Pascal Caversaccio voiced sturdy opposition, following up on his revealed critique: “EOF: When Complexity Outweighs Necessity.” His major declare: No utility builders are asking for EOF, and its rollout dangers alienating the broader dev group.
Regardless of this, EF employees — together with Piper Merriam and Ansgar Dietrichs, in addition to consumer 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.
