jakiro
Author: Macauley Peterson, Blockworks; Compilation: Deng Tong, Bitchain Vision Realm
If there is an Ethereum upgrade was once an eternal bridesmaid, it is EVM Object Format (EOF).
Once engaged and planned to hold a wedding in Shanghai, it was soon abandoned by developers. They were full of expectations for the future of Proto-Danksharding.
If you don’t understand the meaning of this sentence, don’t worry.This is a metaphor for the telephone discussion of the full -core developer of Ethereum for many years.
After the ACD (All Core Dev) conference on Thursday, we still don’t know if EOF will eventually have the opportunity to become a bride.But at least there is a clear proposal on the table.
Developers once strongly considered EOF in Shapella hard forks.However, a year ago, after some thoughts, they decided to give up EOF, but put the focus completely on pledge withdrawal.
Once Shapella is delivered safely, EOF has appeared again in Dencun’s candidate project.Then, it was put on hold again, so that the two main supporters of the function Danno Ferrin and Greg Colvin were regrettable.
The consensus in April 2023 was that EOF was too huge and could not be carried out with EIP-4844 (Proto-Danksharding), so one of them must be selected.The latter finally won the second layer of Rollups with its potential, and finally won.
As a comfort, the Ansgar Dietrichs of the Ethereum Foundation recommends the focus of EOF as the next upgrade.”It is too huge to be the second in the hard fork,” he said.Therefore, it should have its own upgrade.
Dencun, with 4844 as the “driver”, is still expected to enter the main network in March because developers reported the “UNEventful” hard fork of the Sepolia test network on Tuesday.
Before the main network was released, there was only one test network HOLESky. Dencun should receive the final test on February 7.
Officially put EOF on the agenda
On Thursday’s conference on Thursday, the main purpose of the next major functional fork is designed to understand the current state.The consensus layer named “Pragy” was upgraded at the place where DevCon 4 was held.At the same time, “Electra” -this name is inspired by a blue and white superstar in Taurus -it is a term that executes the client to refer to the same upgrade.
The priority of “PECTRA” is slowly emerging.
Ferrin once again promoted EOF, saying that “it is important for EVM in the next few years.”
As the leader of the EOF implementation working group, Ferrin said that developers “have entered the ‘delivery’ model.”
EOF’s goal is to make Ethereum smart contract safer, efficient and more friendly to developers.This is especially important for Ethereum DAPP developers, because they usually do not participate in the full -core developer conference every two weeks.
This has caused some client teams to think that EOF is not important in the past, and this impression has always been difficult to change.
At the call on January 4, Dragan Rakita from the Retro client team strongly support EOF, and Nethermind developer Lukasz Rozmej pointed out that EOF is easier to test than the Verkle tree -this is the main competitive focus of the next fork.
Even the Marius Van der Wijden of Go Ethereum (Geth), once held doubt about EOF, seems to have expressed his relatively supportive ideas.
Van Der Wijden said: “I have been gradually accepting EOF, but it is not the primary task for me.”
At the conference call on January 18, Georgios Konstantonopolous, chief technology officer of Paradigm, said that this is “a person can complete within a few months.”
Ferrin reiterated this view at a recent call meeting that the work of EOF and Verkle was completed by different engineers in the client team, so it promised that the support for EOF would not hinder the progress of Verkle.
However, the Ethereum Foundation’s Geth developer Guillaume Ballet has not been persuaded, and worry that EOF may adversely affect Verkle.
Ballet said: “If it does do first, I need to ensure that we will not publish something, and then find that we are in trouble.”
Andrew Ashikhmin, a software engineer of the Ericon client team, suggested that while making promises on EOF, try on Verkle test online, and draw time to cooperate with Verkle and EOF’s executors in the next few weeks.
This is a bit like the problem of “there is chickens or eggs first”, as Ferrin observed.
“Before we can put it in Verkle’s test network, we need to run it on the client,” he said, and added that his BESU client team might soon make EOF run to test.
But he is convinced that EOF should be compatible with Verkle.
Ballet refutes: “I don’t want to‘ should ’, I want to see it.”
EOF is still trying to grab the bouquet, waiting for the intention to bring it on the red carpet.
