Ethereum developers clash over EOF implementation as network upgrade faces key test

Ethereum developers fight over EVM Object Format (EOF) implementation as the network seeks to upgrade its systems.

The clash started when the network’s Geth team, which primarily tends to Lightclient software, openly objected to including EOF in the Fusaka upgrade.

Ethereum Geth Team wants to exclude EOF from the Fusaka upgrade

Some Ethereum developers have firmly supported the EOF addition to the  Fusaka upgrade, while others are still skeptical of its usefulness. 

Ideally, EOF is meant to make Ethereum applications more efficient and cost-effective while eliminating validation errors. However, some have cited concerns about EOF’s compatibility with Ethereum’s evolving zero-knowledge roll-up technology.

During the February 13 All Core Developers Execution Call, Ethereum’s Geth team commented over the Zoom chat, “We disagree that EOF should be shipped on mainnet at all,”  showing they do not want to integrate EOF with Fusaka upgrade at all. 

However, Geth developer Marius van der Wijden gave a separate opinion from the team, arguing they work mostly as individuals, saying team members should not be obliged to “fall into the party line.”

Before, Van der Wijden openly opposed the EOF implementation for Ethereum’s Pectra upgrade, saying that the object format was very complicated. Last year, he insisted that EOF only makes existing applications slightly faster or cheaper, arguing that its disadvantages outweigh its advantages.

Wijden, however, seems not to care this time around. He stated that if the EOF is implemented, part of his code will be included, which is great, and if it is not implemented, the network will be much safer.

The Pectra upgrade will go live on April 8

As agreed during the All Core Developers Execution Call, Ethereum developers will launch the Pectra upgrade on testnets Holesky and Sepolia on February 24 and March 5, respectively. After that, they will release Pectra on the mainnet on April 8.

However, Tim Beiko, Ethereum Foundation’s Protocol Support Lead, wants the timelines for Fusaka’s upgrade pushed forward, given the rising conflict among developers. He suggested that the final decision on Fusaka should be made by April 10. The Geth team still thinks that the upgrade timeline is too rushed, and making any premature decision could complicate things even further.

Not to mention, ETH developers are still clashing over Ethereum Execution Layer Specifications (EELS) for EIPs. Ethereum Engineer Mario Vega proposed standardized testing through EELS and EEST to increase efficiency; however, some developers are against the idea.

Wijden even claimed that compulsory EELS would give maintainers too much control over EIP approvals, proposing unmerged pull requests for EELS implementations.

BitcoinLinux Academy: Are You Making These Web3 Resume Mistakes? – Find Out Here