Source: Cointelegraph
Original: “Ethereum Fusaka hard fork scheduled for the second half of 2025”
According to an official from the Ethereum Foundation, the Fusaka hard fork for Ethereum is expected to take place in the third or fourth quarter of 2025.
In a post on X on April 28, Tomasz Kajetan Stańczak, co-executive director of the Ethereum Foundation, stated that the organization plans to deploy the Fusaka Ethereum network upgrade in the third or fourth quarter of 2025. However, a specific launch timeline has not yet been determined.
Stańczak mentioned that the controversial implementation of the EVM Object Format (EOF) upgrade is expected to be part of the Fusaka network upgrade, but Ethereum core developer Tim Beiko later ruled out this possibility.
“EOF has been removed from the Fusaka network upgrade today,” Beiko stated in an X post on April 28, and noted in a GitHub post that Ethereum developers decided its impact has technical uncertainties that could delay the launch of Fusaka.
The Ethereum Virtual Machine (EVM) is the software that runs Ethereum smart contracts. EOF will implement a series of protocol changes known as Ethereum Improvement Proposals (EIPs), which will have a profound impact on its operation. EOF introduces a scalable and versioned container format for the bytecode of smart contracts, validated once at deployment, aimed at improving the efficiency of code and data separation.
Bytecode is a set of low-level, compact instructions. Solidity smart contracts must first be compiled into bytecode before they can be executed by the Ethereum Virtual Machine (EVM).
EOF (Ethereum Improvement Proposal) defines a container module for smart contract bytecode, replacing the current free-form bytecode blocks, providing a clearer structure. These objects will consist of the following parts:
This structure simplifies the operation of the EVM, improves efficiency, and reduces processing overhead. This upgrade will lead to a clearer developer environment and more understandable deployed smart contracts.
EIP-4200 is one of the EOF EIPs, providing alternatives to the JUMP and JUMPI instructions, which allow programs to move execution to any arbitrary byte offset. This execution chain can lead to hard-to-detect bugs (in some cases, incorrect JUMP values may be unpredictable) and makes it easy to hide malware in data blocks and move the execution pointer there.
This practice is known as dynamic jumping, and EIP-4750 (under review) proposes to prohibit dynamic JUMP/JUMPI in EOF smart contracts, completely rejecting them in the later stages of EOF deployment. In its current form, this EIP replaces them with calling functions (CALLF) and returning from functions (RETF). These new instructions will ensure that the targets are hardcoded in the bytecode, but legacy pre-EOF smart contracts will remain unaffected.
Developers who choose to use JUMP or JUMPI after the upgrade will have their bytecode validated at deployment, ensuring they cannot jump to the middle of data or other instructions. This validation will be checked through the code validation rules of EIP-3670 and the jump table (EIP-3690), so each target will be verified.
As alternatives to these functions, EOF implements RJUMP and RJUMPI, requiring targets to be hardcoded in the bytecode. However, not everyone supports the implementation of EOF.
EOF is the implementation of 12 Ethereum Improvement Proposals (EIPs), which will have a profound impact on the way smart contract developers work. Its supporters argue that EOF is more efficient, elegant, and allows for easier upgrades in the future.
However, opponents argue that it is overly complex, introducing more complexity to an already complicated Ethereum system. Ethereum developer Pascal Caversaccio stated in a March 13 post on Ethereum Magicians: “EOF is extremely complex,” as it adds two new semantics and removes more than a dozen opcodes. He also believes that it is unnecessary.
He pointed out that all the benefits could be achieved through “more detailed, less invasive updates.” He added that the legacy EVM also needs maintenance, “potentially indefinitely.”
Caversaccio also explained that EOF would require tool upgrades, which could introduce new vulnerabilities due to its larger attack surface. He stated, “With the presence of the header, EVM contracts become more complex,” while the current size of an empty contract is only 15 bytes. Another developer presented a different perspective in the discussion:
“As a meta viewpoint, there seems to be a divide on whether significant EVM changes are necessary. A stable virtual machine that allows people to confidently invest in building great tools and applications seems more valuable.”
Caversaccio does not appear to be alone in his opposition to EOF. A dedicated vote on the Ethereum voting platform ETHPulse showed that 39 voters holding a total of nearly 17,745 Ethereum (ETH) opposed the upgrade. Only 7 voters holding less than 300 ETH supported it.
Related: Researchers propose to increase Ethereum's (Ethereum) fuel cap by 100 times within four years.
免责声明：本文章仅代表作者个人观点，不代表本平台的立场和观点。本文章仅供信息分享，不构成对任何人的任何投资建议。用户与作者之间的任何争议，与本平台无关。如网页中刊载的文章或图片涉及侵权，请提供相关的权利证明和身份证明发送邮件到support@aicoin.com，本平台相关工作人员将会进行核查。
