Ethereum Developers Decide to Exclude EVM Object Format from Fusaka Fork
Ethereum core developers have decided to remove the EVM Object Format (EOF) from the upcoming Fusaka fork after failing to reach a consensus. Key points include:
- The decision was made during an Interop Testing call, which had over 100 participants.
- EOF aimed to address technical debt by improving contract layout and security but faced significant opposition, particularly from application developers.
- Concerns were raised about breaking backward compatibility and added complexity for existing contracts.
- Proponents highlighted EOF's potential benefits for future scalability and migration to new architectures.
- Despite some support for a scaled-back version of EOF, there was no overwhelming consensus to include it in Fusaka.
- The focus will now shift to PeerDAS and other critical scalability improvements.
- A fresh planning process may be needed if EOF is revisited in future upgrades.
Fusaka will proceed without EOF, and the discussions surrounding it may influence Ethereum development for years to come.