ETH the latest progress of the Cancun upgrade

币小白_

ETH Workshop Core Developer Consensus Call (ACDC) is held bi-weekly to discuss and coordinate changes to the ETH Workshop Consensus Layer (CL). During the 122nd ACDC conference call, developers focused on the latest developments in Cancun/Deneb testing and other key topics.

Cancun/Deneb Test Update

Devnet #12的启动: Currently, all Execution Layer (EL) client software such as Teku, Lodestar, and Lighthouse are receiving Devnet #12的测试. The Prysm team expects to have their software ready for testing in the next two to three weeks.

Devnet #11上的验证者退出问题: At the Devnet #11上, developers have identified issues related to validator exits, which are currently being addressed by the Nimbus client team. Until the issue is resolved, Devnet #11将继续正常执行.

Network Specification Clarification: Clarification of the specification for “BlockByRoot” and “BlobSidecarsByRoot” requests to clarify whether Consensus Layer (CL) nodes should respond to these requests in a specific order.

New test tools for Cancun/Deneb upgrades

Devnet #12在2023年11月30日正式启动, “no major issues have been identified to date” among the three CL clients currently running on the test network. Due to Devnet #12的稳定性, Parithosh Jayanthi, a DevOps engineer at the Foundation, asked developers if they should start planning a Goerli shadow fork to further test Cancun/Deneb. However, since the Prysm client software was not yet ready for testing, it was decided to wait for it to be ready.

Devnet #11问题的讨论

The Nimbus developers introduced the Devnet #11的问题细节, which was caused by the “apparent tension” between writing client software in strict accordance with the CL specification in order to test the benefits of coverage and stepping into the gray areas of the specification for better node performance. The developers agreed to add more tests to future Devnets and testnets for a large number of validator exits in Cancun/Deneb.

Network Upgrade Planning Process and EIP Status

The developers also discussed some of the process issues raised by Tim Beiko, Head of Protocol Support for the ETH Foundation, to improve coordination of the ETH Workshop upgrade. Beiko proposes to create an upgrade-specific folder under the ETH Fang repository to organize the various files related to a specific upgrade into a single folder. In addition, it was proposed to create a “Meta EIP” file to track the full scope of the network upgrades that had been completed on the ETH.

EIP Status and CFI Labels

Beiko raised a question about the usefulness of marking ETH Improvement Proposals (EIPs) as “considered to include” (CFI). In the past, this label has done little to no purpose in indicating which EIPs on the EL will be implemented in the upgrade or when. There is no clear consensus on EIP status and CFI labels.

Overall, the ACDC conference call covered topics such as the progress of the Cancun/Deneb testing, Devnet #11的问题解决, the network upgrade planning process, and EIP status and CFI tags, highlighting the continuous improvement and optimization of the ETH protocol.

In the later stage, we will bring you the analysis of the leading projects of other tracks. If you are interested, you can click to pay attention. I will also sort out some cutting-edge inquiries and project comments from time to time, and welcome all like-minded people in the currency circle to explore together. If you have any questions, you can comment and ask questions or send private messages

Source: Golden Finance

Disclaimer: The information on this page may come from third parties and does not represent the views or opinions of Gate. The content displayed on this page is for reference only and does not constitute any financial, investment, or legal advice. Gate does not guarantee the accuracy or completeness of the information and shall not be liable for any losses arising from the use of this information. Virtual asset investments carry high risks and are subject to significant price volatility. You may lose all of your invested principal. Please fully understand the relevant risks and make prudent decisions based on your own financial situation and risk tolerance. For details, please refer to Disclaimer.
Comment
0/400
No comments