Original title: "Ethereum All Core Developers Execution Call #190 Writeup"
Editor's Note:
Ethereum All Core Developers Execution Call (ACDE), held every two weeks, mainly Discuss and coordinate changes to the Ethereum Execution Layer (EL). This is the 190th conference call of ACDE. At this meeting, EIP 7251 and 7702, Ethereum Virtual Object Format (EOF) and PeerDAS were discussed.
During the meeting, Beiko also proposed a new EIP discussion template and emphasized the importance of the Ethereum developer resource page "eth-clients". 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 June 20, 2024, Ethereum developers gathered on Zoom to participate in the All Core Developers Execution (ACDE) call # 190 meetings. 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 presented their progress on implementing various code changes, including Ethereum Improvement Proposals (EIP) 7251 and 7702, as well as Ethereum Virtual Object Format (EOF) and PeerDAS.
Beiko also shared a suggested template for EIP discussions, and EF DevOps Engineer Parithosh Jayanthi introduced a new GitHub page called "eth-clients" for the configuration of the Ethereum mainnet and testnet. Finally, Beiko reminded the team that the next ACDE call will be held during the US holiday of July 4th. While he will not be attending the meeting, EF researcher Alex Stokes will moderate it in his place.
Developers discussed Pectra Devnet 1 at the beginning of the conference. Developers aim to launch the next dedicated testnet for the Pectra upgrade next week. Compared with the previous testnet Devnet 0, the new testnet mainly has the following specification changes:
The EL client team is advancing their Devnet 1 implementation. Representatives from each of the major Ethereum EL teams shared their latest progress:
While the client team was sharing their progress, a developer named "Racytech" asked if the EOF implementation would be excluded from Devnet 1. Beiko confirmed that EOF will not be tested on Devnet 1 and that the EOF implementation should be based on the latest Pectra spec, not the final Deneb spec. EF DevOps Engineer Barnabas Busa emphasized that this strategy will make debugging EOF more difficult because the Pectra specifications are changing and are also being debugged at the same time. "Even so, it's still true because we want the team to work on the core Pectra EIPs and fix those bugs. So, it makes more sense than building on a previous fork and then building on Prague at the final stage, and also discovering all those Wrong," Beiko said. Prague is the EL name for the Pectra upgrade.
While developers are working hard to implement EIP 7702 in Devnet 1, it is possible that significant changes to the code will be made to support new functionality, specifically the ability for users to revoke EIP 7702 transaction authorization.
A Geth developer named "Lightclient" proposed new changes to support the revocation of EIP 7702. He explained: “It’s not easy to see which authorizations you have in effect at any time, and it’s hard to know which ones have been revoked and which ones haven’t. There are design patterns that can avoid these situations, but in reality we may not know what the wallet will do. How to use this feature. To better defend, I remember Vitalik mentioned on the last call, or in a breakout room, that instead of making authorization an ad hoc thing that has to be included in the transaction, we These authorizations can be saved so you can see what codes are assigned to your account at any time. "
A developer named "Arik" stated that he prefers the current version of EIP 7702 to the changes proposed by Lightclient. Arik said there will be some specific use cases under the new EIP 7702. Lightclient disputes these comments, stating that all use cases supported by the older version of EIP 7702 remain, and a powerful undo mechanism has been added. However, Lightclient also pointed out that these changes make the implementation of EIP in the client more complex. Beiko said in the conference chat box that finalizing the EIP 7702 design is Pectra's "number one unresolved spec issue" and suggested the developers organize another breakout call to reach consensus on its revocation mechanism. "It would be nice if by the next meeting we have a version that everyone is generally happy with, whether it's this version or a tweaked version of it, that can be part of Devnet 2," Beiko said.
Besu developer Daniel Lehrner questioned whether developers should spend time implementing the current version of EIP 7702 in Devnet 1 if the specifications are likely to change in Devnet 2. He said: "The proposals are quite different, so we may implement something that in a few weeks will have to be partially discarded due to 7702 changing again." Richard Meissner, co-founder of crypto wallet Safe, said that in his view, It would be helpful for the wallet team to implement some version of EIP 7702 on the testnet. Beiko added that implementation of EIP 7702 in its current form would not, in his opinion, significantly delay the client team's progress, which could cause complications for Devnet 1 if developers now tried to remove it from the Pectra spec.
Speaking of EOF, Busa said his team will test the EOF implementation after implementing other Pectra code changes. EOF readiness is tracked on GitHub. Currently, two EL client teams, Besu and Reth, have implemented all EOF EIPs, while other teams are still working on implementing all EOF EIPs. Representatives from the Erigon team noted that additional test cases simulating Ethereum blocks containing EOF transactions would be useful. Mario Vega, a member of the EF testing team, said in the chat that his team is releasing more EOF tests and will share more at the next EOF breakout session. Danno Ferrin, an independent Ethereum protocol developer, said that since the EOF specification is now finalized, EOF conference calls have been changed from weekly to biweekly, and EOF’s current focus is on testing and client implementation.
Busa gave a brief update on the progress of the PeerDAS implementation. He said the next PeerDAS Devnet will be online in one to two weeks. As discussed at the last ACDC meeting, PeerDAS will be developed based on the finalized Dencun specification, rather than the Pectra specification.
Beiko has proposed a new default template for EIP authors to use in Ethereum Magicians posts. This new template is designed to facilitate high-quality reviews of EIPs.
Jayanthi introduced the "eth-clients" GitHub page, which provides a variety of resources for Ethereum developers, including standard configurations for the Ethereum testnet and mainnet. Currently, this page is maintained by representatives from all CL client teams. Jayanthi called on representatives from the EL client team to volunteer to help maintain this GitHub page.
Lightclient asked the client team about the progress of the work on historical data expiration. No updates on this were shared at the meeting.
Beiko says he will not host the next ACDE conference call, which falls on the US holiday, July 4th. He will then be chaired by EF researcher Alex Stokes.
The above is the detailed content of Ethereum Core Developers Latest Meeting Summary: Pectra Upgrade's Next Private Testnet Launched Next Week. For more information, please follow other related articles on the PHP Chinese website!
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
