Ethereum core developers have made a critical decision to exclude the EVM Object Format (EOF) from the upcoming Fusaka fork. The decision, following extensive discussions and a lack of consensus, highlights the debates over scalability and developer experience in the Ethereum ecosystem. Despite technical support for EOF aimed at addressing long-standing issues in contract execution and security, opposition grew primarily among application developers and members of the Vyper compiler team. Key concerns included the breaking of backward compatibility and potential disruptions to significant Solidity libraries. Ultimately, Ethereum's governance prefers pragmatic decisions, recognizing that core developer consensus is essential. Many participants expressed that due to the divisions over EOF, it would not be integrated into Fusaka. The focus will now shift to enhancements in PeerDAS and other scalability solutions. Moving forward, the future of EOF remains uncertain, and further discussions are expected as the community evaluates its potential reintroduction in subsequent upgrades.

Source đź”—