According to an official of the Foundation of the Ethereum Foundation.
In an article of April 28, the director of the Executive Director of the Ethereum Foundation, Tomasz Kajetan Stańczak, said that the organization was aimed at upgrading the Fusaka Ethereum network in the third quarter or the fourth quarter 2025. Still, the exact deployment calendar has not yet been decided.
The comments come in the middle of the controversies on the next implementation of the upgrading of the EVM object format (EOF) for the Ethereum virtual machine (EVM). As Stéńczak pointed out, the EOF should be part of the upgrade of the Fusaka network.
The EVM is the software that performs Ethereum intelligent contracts. The EOF would implement a series of protocol changes, known as Ethereum improvement proposals (EIPS), with deep implications on its operation. EOF introduces an expandable container format and paid for the cocoton of the intelligent contract which is checked once to deploy, separating the code and data for efficiency gains.
In relation: The researcher offers the scale of the Ethereum gas limit of 100 times over 4 years
Wrap, stamp once, send
Bytecode is a set of compact low level instructions. Solidity Smart Contracts must be compiled in bytecode before the EVM can execute them.
EOF defines a container module for intelligent contract bytecodes, replacing the BYTECODE BLOSCODE today by a better defined structure. These objects are said to be composed of:
-
A header starting with the hexadecimal value 0xef00, followed by a version number of an byte to ensure the upgrade.
-
A section table, providing metadata on the contents of the container. Each input includes an byte parameter for the input type and two bytes for the size of the input.
-
Sections with the real content, with at least one code section and all the necessary data sections – more types of sections can be added via future EIP.
This structure rationalizes the functioning of the EVM, allowing higher efficiency and general costs of lower treatment. This upgrade would cause a cleaner and easier developer environment to understand and understand intelligent contracts.
Don’t jump instead!
EIP-4200, one of the EIP EIP, provides an alternative to the Jump and Jumpi instructions, which allow the program to move the execution to any arbitrary byte gap. This type of execution chain leads to difficult to stains bugs (the jump value due in certain cases may not be easy to predict) and facilitates the hiding place of malware in data blobs and move the execution pointer there.
This practice is known as dynamic jump, and EIP-4750 (being examined) proposes to prohibit dynamic jump / Jumpi in EOF intelligent contracts, rejecting them entirely during a subsequent EOF deployment phase. In its current form, this EIP replaces them with the call function (CALLF) and the function of the function of the function (RETF). These new instructions would guarantee that the destinations are coded in hard in Bytecode, but the inherited intelligent contracts inherited would not be affected.
Developers who choose to use Jump or Jumpi after upgrading will have their bytecode go through the validation of deployment, which guarantees that they can never jump into the data or in the middle of another instruction. This verification would take place via the EIP-3670 code validation rules, plus the jump table (EIP-3690), so that each destination is verified.
As an alternative to these functions, EOF implements Rjump and Rjumpi instead, which require that the destination be coded in hard in Bytecode. However, not everyone is aboard the implementation of the EOF.
In relation: The members of the Ethereum community offer a new cost structure for the application layer
EOF has its enemies
EOF is the implementation of 12 EIP with deep implications on the functioning of developers of intelligent contracts. His supporters argue that it is effective, more elegant and allows easier upgrades on the line.
However, his detractors argue that he is over-designed and introduces additional complexity in an already complex system like Ethereum. The developer of Ethereum Pascal Caversaccio deplored in a post of Ethereum Magicians of March 13 that “the EOF is extremely complex”, because it adds two new semantics and suppresses and adds more than a dozen opcodes. He also argued that it was not necessary.
He said that all the advantages could be introduced into “more fragmentary and less invasive updates”. He added that the inherited EVM should also be maintained, “probably indefinitely”.
Caversaccio also explained that the EOF would require an upgrade of tools, which risks introducing new vulnerabilities because of its large attack area. He also said that “EVM contracts are becoming much more complicated due to headers”, while empty contracts are currently weighing only 15 bytes. Another developer raised a separate point in the wire:
“Perhaps as a meta point, there seems to be a disagreement on the question of whether the major EVM changes are desirable in general. A stable virtual machine, on which people can invest in the creation of excellent tools and applications with confidence, is much more precious.”
Caversaccio seems to be in good company in his opposition to EOF. A dedicated survey on the Ethereum Ethpulse survey platform shows that 39 voters holding a total of nearly 17,745 ether (ETH) are opposed to upgrade. Only seven holders of less than 300 ETH voted in favor.
Review: Ethereum destroys competition in the tradfi tokenization race of 16.1 t $
