Blog

Ethereum Fusaka scheduled for late 2025: The EVM upgrade is likely to be listed

cryptobizinvest.com April 28, 2025

0 0 3 minutes read

Fusaka Hard Fork is expected to be from ETAREUM in the third or fourth quarter of this year, according to the ETHEREUM Foundation official.

On April 28 x mailThe CEO of Ethereum Tomasz Kajetan Stańczak said that the organization aims to spread the upgrade of the Fusaka ethereum network in the third quarter or Q4 2025. However, the exact scroll schedule has not yet been determined.

Comments come amid the differences about the upcoming implementation of the EVM (EOF) object (EOF) Promoted to Ethereum (EVM) virtual device (EVM). Staczak also indicated, EOF is expected to be part of the fusaka network upgrade.

EVM is the program that runs Ethereum Smart contracts. EOF will implement a series of protocol changes, known as the ETHEREUM (EIPS) proposals, with profound effects on how they work. EOF provides an expandable and expandable container container for the Bytecode system that is verified once in publishing, separating the code and data to achieve efficiency gains.

Wrap, seal once, send

Bytecode is a set of low -level instructions. Smart contracts for hardness in bytecode should be assembled before EVM can implement them.

EOF defines a container of the Bytecode Smart Contracted program, replacing the free -shaped beangots today with a better specific structure. These creatures will consist of:

A head starts from the hexagonal value of 0xef00, followed by one byte version to ensure an upgrade.
Division schedule, provides definition data on the contents of the container. Each input includes one byte preparation for the type of input and two of the guns for the size of the input.
Sections containing actual content, with at least one symbol section and any necessary data sections – more sections can be added through future EIPS.

This structure simplifies the EVM process, allowing higher efficiency and reducing public expenses. This upgrade will lead to a cleaner and easy -to -understand environment.

Do not jump, RJOMP instead!

EIP-4200EOF EIPS provides an alternative to jumping and jumping instructions, which allows the program to transfer implementation to any arbitrary gun. This type of implementation chain leads to difficult errors (it may not be easy to predict the wrong value in some cases) and makes it easy to hide harmful programs in data operations and transfer the implementation indicator there.

This practice is known as the dynamic jump, and EIP-4750 (Under the review) suggests that the dynamic jump/jump into the EOF smart contracts is not heard, and it is fully rejected during a later stage of the publication of EOF. In its current form, EIP replaces them with the contact function (Call) and the return of the functionality of the job (RETF). These new instructions will guarantee that the destinations are strict in the Bytecode code, but the smart contracts before the judicial Eof will not be affected.

The developers who choose to use Jump or Jumpi after upgrade will get the time to verify time, ensuring their inability to jump into data or mid -instructions. This verification will happen via EIP-3670Code validation rules, in addition to the jumping table (EIP-3690) Therefore, each destination is examined.

As an alternative to these functions, EOF performs RJOMP and RJOMPI instead, which requires the destination to be coded in the Bytecode icon. However, not everyone is on board EOF.

EOF has her hate

EOF is the implementation of 12 EIPS with profound effects on how smart contract developers work. Its supporters argue that they are effective and more elegant, and they allow easier upgrades below the line.

However, its critics argue that it is excessively designed and provides more complexity in a already complex system like Ethereum. Unfortunately, Ethereum Pascal Capersaccio developer on March 13 of Ethereum magicians mail The “EOF is very complex”, as it adds a new significance, removes and adds more than ten OPCodes. Also, he argued that it is not necessary.

He said all the benefits can be provided in “more gradual and less invasive updates.” He added that the EVM inheritance will also need to preserve it, “perhaps indefinitely.”

Caversaccio also explained that EOF will require the promotion of tools, which risk introducing new weaknesses The surface of the attack. He also said: “EVM contracts become more complicated by the heads,” while the empty contracts currently weigh 15 byte. Lift the last developer separate point in the topic:

“Maybe as a dead point, it seems that there is a dispute over whether the main EVM changes are generally desirable. VM is stable, people can invest on it in building excellent tools and applications with confidence, more valuable.”

Capersaccio appears to be in a good company in his opposition to Eof. Dedicated reconnaissance On the ETHEREUM polling platform, Ethpulse explains that 39 voters carry approximately 17,745 ether (ETH) oppose the promotion. Voice of seven owners less than 300 ETH in favor.