Summary of the latest meeting of Ethereum core developers: Preparing to implement EIP 3074, Rollup roadmap

Original title: "Ethereum All Core Developers Execution Call #186 Writeup"

Original author: Christine Kim

Original compilation: Frost, BlockBeats

Editor’s note:

The All Core Ethereum Developers Consensus Call (ACDE) is held every two weeks to discuss and coordinate changes to the Ethereum Execution Layer (EL). During ACDE's 186th conference call, developers discussed preparations for Pectra Devnet 0 and EIP 3074 implementation. They detailed the progress of various customer teams in preparing for Pectra Devnet 0 and discussed proposed changes to the EIP 3074 specification and related testing progress.

In addition, this article also touches on other important topics, such as a discussion of other code changes that may be included in the Pectra upgrade, and a discussion of how changes to the Ethereum EIP process are affected by the L2/RIP process. Christine Kim, vice president of research at Galaxy Digital, recorded the key points of this meeting in detail, and BlockBeasts compiled the original text as follows:

On April 25, 2024, Ethereum developers gathered on Zoom to participate in the All Core Developers Execution ( ACDE ) call #186 meeting. The ACDE Conference Call is a biweekly series of meetings hosted by Tim Beiko, Head of Protocol Support at the Ethereum Foundation, where developers discuss and coordinate changes to the Ethereum Execution Layer (EL). This week, developers discussed preparations for Pectra Devnet 0 and EIP 3074 implementation. They also discussed what other EIPs should be considered for inclusion in Pectra upgrades, as well as broader thoughts on governance changes given Ethereum’s “Rollup-centric roadmap.”

Pectra Devnet 0 Latest Progress

Beiko asked the account team during the conference call to share the latest progress on Pectra Devnet 0. Marek Moraczyński from the Nethermind team said that Nethermind has implemented all Pectra EIPs and is testing them. Justin Florentine of the Besu team said Besu is implementing the Pectra EIP and working with them to prepare for the Devnet 0 rollout. Andrew Ashikhmin of the Erigon team said, "I'm not sure whether Erigon is ready for the number of EIPs for the full suite of Devnet 0, partly because the specifications for these EIPs are still changing and the Erigon client is transitioning to the new major version Erigon 3. This takes up the team's resources and time as Erigon 3 and Pectra EIP are finalized and built into the Erigon client together." The Geth team’s “Lightclient” said Geth is “a few days away” from being ready for Devnet 0. Gajinder Singh of the Ethereum JS team said that Ethereum JS will also be "ready" for Devnet 0.

EIP -7685

Lightclient incorporates EIP 7685, which creates a common framework for storing EL-triggered requests into the Consensus Layer (CL) and its support for EIP 6110 and 7002 Influence. Beiko said developers should include this EIP in their Devnet 0 releases and continue to improve the Pectra EIP.

In terms of testing, Mario Vega of the EF testing team said that testing of EIP 6110 and 2537 has been completed, and testing of EIP 7002 and EIP 2935 will be completed this week or next week. Testing of EIP 3074 is not yet ready for Devnet 0. EF researcher Antonio Sanso said that the EIP 2537 specification has been updated and new test vectors have been added to the GitHub repository, and he recommends everyone to check it out on GitHub. EF researcher Hsiao Wei Wang pointed out that there was an error in the CL specification test vector, so the error was quickly fixed and a new version was released.

Updates for EIP -3074

This week's ACDE call for EIP 3074 specifications proposes several changes. Ahmad Mazen Bitar suggested changing the behavior of EIP 3074 to allow DELEGATECALL before AUTH CALL, which would expand the use cases of EIP. Derek Jiang, founder and CEO of blockchain wallet operating system ZeroDev, suggested creating a “noncemanager” to facilitate global revocation of AUTH messages and other changes when needed. Some developers on the call believed changes to EIP 3074 should be delayed because they would make it significantly more difficult to implement.

Beiko recommends that developers discuss proposed changes to EIP 3074 in separate breakout sessions. He noted that in order to have enough time to implement EIP 3074 in Pectra, developers should try to finalize its specifications "in the next month or two." Lightclient agrees to organize an EIP 3074 breakout session. For Devnet 0, Beiko confirmed that customer teams should implement EIP 3074 without any changes, even though developers may decide that future devnets implement EIP differently or remove it entirely from upgrades.

In addition to the implementation details of EIP 3074, developers also seriously discussed whether EIP has sufficient community support. One developer whose screen name is "Siri" expressed concern during the call that "EIP 3074 is bad in principle and will slow down our ability to achieve full account abstraction." Beiko responded that based on Ethereum Magician and ACD call discussions, the account team appears to support EIP 3074 over other proposals related to Account Abstraction (AA). Beiko said: "This seems to be the most consensus proposal in the short term, and we can actually improve the status of EOA in the next fork." In this regard, Siri believes that the customer team should not make this decision in isolation. “We should listen to other stakeholders,” Siri said, adding, “We don’t want to veer into the realm of creating contentious hard forks. … I think it would be good to understand what other stakeholders are saying and how they view this. Proposal."

Beiko and Siri also discussed how to build broader consensus for EIP beyond the ACD call. Chiang suggested first holding an EIP 3074 breakout meeting to discuss the EIP's technical specifications in depth and then decide whether it should remain in the Pectra upgrade. EF researcher Ansgar Dietrichs said, "We should understand that unless we make enough progress, EIP 3074 will be withdrawn."

Ethereum co-founder Vitalik Buterin added, "User accounts in the next few years There are upcoming changes to functionality, specifically the activation of account abstraction related EIPs such as EIP 3074 etc."

Other Pectra proposals

The developers continue to discuss which ones should be considered. Other code changes are included in the Pectra upgrade. Geth developer Marius van der Wijden said it should depend on whether higher-complexity EIPs like EOF make their way to Pectra. "If we were to include EOF, that would lead to fork saturation. If we didn't include EOF, maybe we could include more," van der Wijden said.

Siri expressed concern about the inclusion of EIP 3074 in Pectra without a security review. Beiko suggested putting this discussion on hold until the specifications for EIP 3074 are finalized.

Bitar said he would like to see EIP 7212 added to Pectra. EIP 7212 will create a new precompile that performs signature verification in secp256 r1 elliptic curves. This can be used with hardware devices that support user biometrics. Bitar said that supporting biometrics to sign Ethereum transactions would be a major improvement to the user experience. Ashihemin said he also supported the proposal. Dietrichs pointed out that this is the only solution approved for implementation by Layer-2 Rollups through the "Rollup Improvement Proposal" (RIP) process.

Other developers including Dietrichs, van der Wijden and Moraczyński have expressed support for EIP 7623, which would increase the cost of call data and thus limit the maximum block size. Beiko recommends marking EIP 7623 and EIP 7212 as "for consideration" or CFI into Pectra, and revisiting the client team's bandwidth to support these two improvement proposals after Devnet 0 launches.

Regarding the EIP bundle related to updating EL's serialization method to SSZ, van der Wijden expressed concern that these would be too difficult to transport in Pectra. His colleague on the Geth team, Guillaume Ballet, agrees with this assessment. Buterin chimed in, saying that at least a serialization method for updating transaction receipts would have "significant value" beyond Ethereum itself, as it eliminates the additional security auditing overhead of layer 2 rollups built on top of Ethereum. ”. The main backer of the SSZ-related EIP, Etan Kissling from the Nimbus team, was not present on the call, but he wrote a detailed explanation on GitHub about why these code changes are important and should be considered for inclusion in Pectra .

The developers also revisited EOF. Danno Ferrin, an independent Ethereum protocol developer, said that the EOF team is conducting EL specification testing on code changes. EVMOne and Reth are two EL client teams that have reportedly completed EOF implementations. Ferrin said the Geth team has made "good progress" on the implementation. Ferrin added that Ballet is working with "Daniel" from the Solidity team to address concerns about EOF and Verkle compatibility.

Ballet noted that based on his conversations with other developers such as Daniel and Dietrichs, it would be difficult to narrow down the scope of EOF without defeating its purpose and provide developers with the opportunity to implement another set of EOF-like code in the future Change creates more jobs.

A developer whose screen name is "Charles C" suggested looking for a way to easily implement EOF iteratively via a Side Car mechanism (such as that used for Blob transactions) rather than on small or large Choose between EOF upgrades. Dietrichs asked in the chat whether account teams would be more interested in Pectra if its EOF complexity were reduced. The Ipsilon team noted that the code changes that caused the highest complexity in EOF (such as "TX create") have been resolved, and removing specific requests for functions such as "EOF create" will not significantly reduce overall EOF complexity. For context, Ipsilon is the name of the EF-funded EVM R&D team. Beiko recommends that developers continue to discuss EOF implementations in the recurring EOF breakout sessions.

ACD/EIP and L2/RIP

As the last topic discussed in ACDE #186, the developers discussed changes to the Ethereum EIP process to consider the new RIP process. Dietrichs noted that it's been six months since the developers started a meeting series on Rollup coordination, RollCall and RIP processes. There are currently some open questions about how these processes will and should impact the Ethereum EIP process. Dietrichs said that one ongoing research question in L2 is whether long-term equivalence to the Ethereum Virtual Machine (EVM) is desirable for Rollup. He also added that an open question is the extent to which changes implemented on L2 will ultimately impact protocol decisions at Ethereum’s Layer 1.

Geth developer Péter Szilágyi stated that some features provided on L2 may not be suitable for provision on L1, and in some cases, even if the features provided on L2 are followed, there may be differences between L2 Different, this may cause confusion for Ethereum protocol developers. EF researcher Carl Beekhuizen pointed out that the RollCalls and RIP process do not require Ethereum protocol developers to release any features on L2, but rather improve communication between Rollups and Ethereum developers in order to avoid confusing situations like the one described by Szilágyi . Van der Wijden expressed concern that protocol developers spend time supporting changes implemented on L2 that will eventually become obsolete or unnecessary as L2 itself shuts down or ceases to be used.

Regarding these concerns, Dietrichs said: "I think people have always thought that Layer 2 can experiment and get crazier. I think what we see in practice is that most of them decide not to. did, or at least probably started doing that, and then over time, most people stopped doing that, so now they're actually mostly following the first layer spec, I think at least given the Rollup-centric roadmap, or so we do. We all agree that this is the best way for the ecosystem to develop, and we owe at least clear guidance and communication from Layer 2 as to the best path forward here.”

The above is the detailed content of Summary of the latest meeting of Ethereum core developers: Preparing to implement EIP 3074, Rollup roadmap. For more information, please follow other related articles on the PHP Chinese website!