Original Title: "Ethereum All Core Developers Execution Call #173 Writeup"

Original Author: Christine Kim, Vice President of Research at Galaxy Digital

Translated by: Sharon, BlockBeats

Editor's note: On October 26th, Ethereum developers gathered on Zoom for All Core Developers Execution (ACDE) Call #173 to discuss the latest developments in Ethereum.

This ACDE conference call was hosted by Tim Beiko, the protocol support manager of the Ethereum Foundation. Developers discussed and coordinated changes to the Ethereum Execution Layer (EL) during the meeting. The developers discussed:

· The launch of Devnet-10

· Blob latency analysis conducted by the Teku (CL) client team.· Dencun Testing Follow-up Steps· L2 rollup standardization work· EIP 7523, deprecated empty accounts.

Devnet-10

The developers launched Devnet-10 on Monday, October 23 to test the Cancun/Deneb (Dencun) upgrade. The development network created 330,000 active validators to trigger changes to the validator churn limit. The validator churn limit change mechanism outlined in EIP 7514 is working as expected on Devnet-10.

The DevOps engineer of the Ethereum Foundation, Barnabas Busa, mentioned that some errors were found in the Prysm and Teku (CL) clients after the release of Devnet-10. These issues (click the link for details) have now been resolved. Developers also tested the complete MEV workflow on Devnet-10 using the Lodestar (CL) client. Busa noted that some issues were found in the MEV-Boost validator and relay implementation. Developers are testing the MEV workflow on other CL clients.

Blob Delay Analysis

The developer of Teku CL client, Enrico Del Fante, shared new analysis on blob latency on Devnet-10. Del Fante stated that his findings confirmed the trend discovered by software developers Gajinder Singh, who maintain the Lodestar and EthereumJS clients, on Devnet-9 and shared during last week's ACD conference call.

Fante encourages every CL client team to carefully examine the parallelism level of their client on the peer-to-peer layer between blocks and gossip blobs. Developers also agreed that more analysis and testing should be done on the propagation of blobs for the upcoming testnet. However, "Potuz," an anonymous developer of the Prysm (CL) client, stated that client versions should first stabilize on the development network before conducting the same type of analysis on public Ethereum testnets like Goerli.

Aside from a stable client version, Terence Tsao, a developer for the Prysm (CL) client, suggests that more testing should be done on the MEV builder and relay before the Dencun public testnet is released. Busa noted that due to the scale of Devnet-10 and the cost of maintaining a developer-centric testnet, developers plan to shut down Devnet-10 before Monday, October 30th.

However, Busa said that instead, developers can launch the 11th development network supported by a smaller number of validators. Potuz agrees to establish another development network after Devnet-10.

Dencun Testing Follow-up Steps

除了推出 Devnet-11 之外，开发人员还同意推出 Goerli 测试网的影子分叉。作为背景，影子分叉是一种以开发人员为中心的测试网络，通过分叉具有少量节点的实时网络而创建。有关 Tim Beiko 撰写的影子叉的更多信息可以点击链接查看。

In addition to launching Devnet-11, developers have also agreed to launch a shadow fork of the Goerli testnet. As background, a shadow fork is a developer-centric test network created by forking a live network with a small number of nodes. More information about the shadow fork written by Tim Beiko can be found by clicking on this link.

In an ideal scenario, Devnet-11 will test the MEV workflow of all CL clients and test at least one rollup implementation, most likely Optimism's rollup implementation for EIP 4844, as well as a stable client version. If all three of these things can be achieved on Devnet-11, the developers agree to launch Dencun on Goerli afterwards.

Later, the developers discussed the launch time of Devnet-11, the Goerli testnet fork, and the activation of Dencun on Goerli. Parithosh Jayanthi, the DevOps engineer at the Ethereum Foundation, said that his team may launch the Goerli testnet fork in the coming week before the ACD conference call.

Busa suggested that the target activation date for Decun on Goerli be November 9th, Thursday. However, this date was quickly vetoed by Potuz due to the "depth" of changes still being pushed to the Prysm client software. Busa stated that it would not be wise to set the activation date for Dencun on Goerli one week after the Ethereum developer conference Devconnect, which will be held from November 13th to 17th.

According to the discussion, developers are very clear that the earliest upgrade of Dencun will not be activated on Goerli until the end of November. Historically, the activation interval of Ethereum's test network upgrade is two weeks. For example, if Decun is activated on Goerli at the end of November on Wednesday, November 22, it means that the next two test network upgrades on Sepolia and Holesky will be conducted in early and mid-December respectively.

This schedule assumes no major issues are discovered between now and the activation of the testnet. Tim Beiko noted that even with the most ideal schedule, Decun's mainnet would likely activate during the holiday season in late December. It is most likely that developers will delay the activation of the upgraded mainnet for Dencun until early 2024.

KZG Ceremony Verification and L2 Standardization

Then, Carl Beekhuizen, a researcher from the Ethereum Foundation, briefly introduced his work on formatting the output for the KZG ceremony and the start of monthly conference calls between Layer-2 rollup developers.

Regarding the KZG ceremony for EIP 4844, Beekhuizen stated that the final output of the ceremony has been fully formatted. He encourages individuals who have contributed to the ceremony to verify that their output has been correctly recorded by visiting the ceremony website or running this command-line interface verification tool. For background information on the EIP 4844 KZG ceremony, please read this report.

Secondly, Beekhuizen emphasized that he hosted the first "Rollcall" on Wednesday, October 18th, which is a dedicated conference call between Layer-2 rollup teams to discuss the specifications and standards for rollup development. These conference calls will continue to be held monthly.

Participants in the Layer-2 phone conference discussed potential changes to the EVM and APIs for the interface between the Ethereum mainnet and rollups. Next month, Devconnect will also hold an in-person gathering for L2 rollup teams. For more information on the in-person rollcall meeting, please click here.

EIP 7523, Abolishing Empty Accounts

Finally, Danno Ferrin from Swirlds Labs, the development team behind Hedera Hashgraph, raised questions about EIP 7523, which proposes to prohibit any state of Ethereum test networks from including empty accounts after the merge. Empty accounts no longer exist on the Ethereum mainnet and are explicitly prohibited from entering any Ethereum testnet with a merged environment, aiming to reduce technical debt caused by such deprecated accounts.

Besu (EL) developer Justin Florentine supports EIP. Ethereum Foundation researcher Dankrad Feist questions whether EIP will affect the implementation of Verkle trees in any way. Beiko encourages developers to continue discussing potential compatibility issues with EIP and any other code changes in the dedicated Ethereum Magicians thread for EIP 7523. For more information, please click here.

Welcome to join the official BlockBeats community:

Telegram Subscription Group: https://t.me/theblockbeats

Telegram Discussion Group: https://t.me/BlockBeats_App

Official Twitter Account: https://twitter.com/BlockBeatsAsia