On October 26th, Ethereum developers gathered on Zoom for All Core Developers Execution (ACDE) Call # 173. The ACDE conference call is hosted by Tim Beiko, Director of Protocol Support at the Ethereum Foundation, and a series of meetings are held every two weeks where developers discuss and coordinate changes to the Ethereum Execution Layer (EL)
On October 26th, Ethereum developers gathered on Zoom for All Core Developers Execution (ACDE) Call # 173. The ACDE conference call is hosted by Tim Beiko, Director of Protocol Support at the Ethereum Foundation, and a series of meetings are held every two weeks where developers discuss and coordinate changes to the Ethereum Execution Layer (EL). This week, developers discussed:
-The launch of Devnet-10 in the development network - Blob latency analysis conducted by the Teku (CL) client team - Next steps in the Encun testing - Layer 2 summary standardization work - EIP7523, discarding empty accounts.
1. Devnet-10
Developers launched Devnet-10 on Monday, October 23rd to test the Cancun/Deneb upgrade. The development network created 330000 active validators to trigger changes in validator churn limits. The validator churn limit change mechanism outlined in EIP7514 works as expected on Devnet-10.DevOps engineer Barnabas Busa from the Ethereum Foundation mentioned that after the release of Devnet-10, some errors were found in Prysm and Teku (CL) clients. These issues (see details)here. The developers also tested the complete MEV workflow on Devnet-10 using the Lodestar (CL) client. Busa mentioned that some issues were found in the MEV-Boost validator and relay implementation. The developers are testing the MEV workflow on other CL clients.
2. Blob Delay Analysis
TekuCL client developer Enr1C0DelFante shared a new analysis on blob latency on Devnet-10. DelFante stated that his findings confirm the trends discovered by software developer GajinderSingh, who maintains Lodestar and Ethereum JS clients, on Devnet-9, which were shared during last week's ACD conference call.Fante encourages each CL client team to carefully examine the level of parallelism between their clients' blocks and blobs at the peer-to-peer layer. Developers also agree that more analysis and testing should be conducted on the blob propagation of the upcoming testing network. However, anonymous developer "Potuz" from the Prysm (CL) client stated that before conducting the same type of analysis on public Ethereum test networks like Goerli, the client version should first stabilize on the development network.
In addition to a stable client version, Terence Tsao, a developer of Prysm (CL) client, stated that,More testing should be conducted on the MEV builder and relay before starting the public testing network release for Denchun. Busa pointed out that due to the scale of Devnet-10 and the cost of maintaining the normal operation of a developer centered testing network, developers plan to shut down Devnet-10 before Monday, October 30th. However, Busa stated that instead, developers can initiate an 11th development network supported by a smaller number of validators. Potuz supports the establishment of another development network after Devnet-10.
3. Next steps for Denchun testing
In addition to launching Devnet-11, developers also agreed to launch a shadow fork for the Goerli test network. As a background, shadow forking is a developer centric testing network created by forking a real-time network with a small number of nodes.More information about ShadowForks written by Tim Beiko can be found here.
Ideally, Devnet-11 will test the MEV workflow of all CL clients and at least one aggregated implementation, most likely Optimism's aggregated implementation for EIP4844 and a stable client version. If all three of these things can be implemented on Devnet-11, the developers agree to subsequently launch Denchun on Goerli.
Subsequently, the developers discussed the startup time of Devnet-11, Goerli shadow fork, and Denchun activation on Goerli.Paritosh Jayanthi, a DevOps engineer at the Ethereum Foundation, stated that his team may launch Goerli's Shadow Bifurcation early next week before next week's ACD conference call. Busa suggests that the target activation date for Decun on Goerli is Thursday, November 9th. However, considering the number of "deep" changes still being pushed to the Prysm client software, this date was quickly rejected by Potuz because it was too ambitious. Busa stated that considering that the Ethereum Developer Conference Devconnect will be held from November 13th to 17th, it would be unwise to set the activation date for Denchun on Goerli to one week later.
According to the discussion, developers are well aware that the upgrade of Denchun will not be activated on Goerli until the end of November at the earliest. From a historical perspective, the activation interval for Ethereum upgraded test networks is two weeks. For example, on Wednesday, November 22nd, Decun was activated on Goerli at the end of November, which means that the next two test network upgrades on Sepolia and Holesky will take place in early and mid December, respectively. This schedule assumes that no significant errors were found between the activation of the test network. TImBeiko pointed out that even with the most ideal schedule, Decun's main network will be activated during the holiday period in late December. Most likely, developers will postpone the activation of the main network for the Denchun upgrade until early 2024.
3. KZG ceremony validation and two-layer standardization
Then, Carl Beekhuizen, a researcher from the Ethereum Foundation, briefly introduced his work on formatting output for KZG ceremonies and the beginning of a monthly series of conference calls between Layer2Rollup developers.
Regarding the KZG ceremony of EIP4844, Beekhuizen pointed out that the final output of the ceremony has been fully formatted. He encourages individuals who contribute to the ceremony to verify whether their output has been correctly recorded by visiting the ceremony website or running this command-line interface verification tool. For the background of the EIP4844KZG ceremony, please read this Galaxy Research report.
Secondly, Beekhuizen emphasized that he hosted the first "Rollcall" on Wednesday, October 18th, which was a dedicated conference call between the Layer2Rollup team to discuss the specifications and standards for Rollup development. These calls will continue to occur every month in the future.Participants in the Layer2 conference call discussed potential changes in EVM and the API used for the interface between the Ethereum main network and aggregation.Next month, Devconnect will also hold an on-site gathering for the Layer2Rollup team.
4. EIP-7523, Abandoning Empty Account
Finally, DannoFerrin from SwirldsLabs, the development team behind HederaHashgraph, raised the issue regarding EIP-7523, which proposes to prohibit any Ethereum testing network from including empty accounts after consolidation.There are no longer empty accounts on the Ethereum main network and they are explicitly prohibited from entering any Ethereum testing network with a merged environment, with the aim of reducing technical debt caused by such abandoned accounts. Besu (EL) developer Justin Florentine supports EIP. DankradFeist, a researcher at the Ethereum Foundation, questions whether EIP will affect the implementation of the Verkle tree in any way. Beiko encourages developers to continue discussing EIP and any potential compatibility issues with other code changes in the EIP7523 dedicated Ethereum Magician thread. Relevant information can be accessed at (EIP-7523: EmptyAccountsdeplication).
Disclaimer: The content of this article is sourced from the internet. The copyright of the text, images, and other materials belongs to the original author. The platform reprints the materials for the purpose of conveying more information. The content of the article is for reference and learning only, and should not be used for commercial purposes. If it infringes on your legitimate rights and interests, please contact us promptly and we will handle it as soon as possible! We respect copyright and are committed to protecting it. Thank you for sharing.(Email:[email protected])
