One of the notable enhancements of EOF is a new container format for smart contract bytecode, which improves efficiency by separating code and data and requiring verification only at deployment.

As of now, the exact rollout schedule for the Fusaka upgrade has not been finalized, leaving some uncertainty among developers and stakeholders.

EIP-4200 proposes an alternative to the existing JUMP and JUMPI instructions, aiming to reduce bugs and security risks in smart contracts.

However, opponents like developer Pascal Caversaccio argue that EOF adds unnecessary complexity and could introduce new vulnerabilities, advocating for smaller, less invasive updates instead.

A recent poll on the Ethereum platform ETHPulse revealed significant opposition to EOF, with 39 voters representing nearly 17,745 Ether against the upgrade, while only seven smaller holders supported it.

Ethereum's Fusaka hard fork is set to take place in the latter half of 2025, as confirmed by Tomasz Kajetan Stańczak, co-executive director of the Ethereum Foundation.

A key feature of the Fusaka upgrade is the implementation of the Ethereum Virtual Machine object format (EOF), which introduces significant changes to the EVM.

Developers utilizing the JUMP or JUMPI instructions after the upgrade will need to undergo deploy-time validation to mitigate vulnerabilities.

EOF is composed of 12 Ethereum Improvement Proposals (EIPs) aimed at enhancing the smart contract development process, although it has faced criticism for potentially over-engineering.

The structure of EOF includes a header, a section table for metadata, and designated sections for code and data, which collectively aim to enhance the operation of the EVM and improve the developer experience.