Research Summary
The report discusses the Ethereum All Core Developers Consensus (ACDC) call #123, where Ethereum developers discussed updates on Cancun/Deneb testing, including the launch of Devnet #12 and issues with Devnet #11. The developers also discussed networking specifications clarification and process improvements for Ethereum upgrades.
Key Takeaways
Updates on Cancun/Deneb Testing
- Launch of Devnet #12: The Ethereum developers are currently testing Teku, Lodestar, and Lighthouse client software on Devnet #12. The Prysm team expects to have their software ready for testing on the latest Devnet in two to three weeks.
- Validator Exit Issue on Devnet #11: An issue with validator exits on Devnet #11 was identified and is being resolved by the Nimbus client team. Devnet #11 will continue to operate until the issue is fixed.
- Networking Specifications Clarification: The developers discussed clarifying specifications for the “BlockByRoot” and “BlobSidecarsByRoot” requests to clearly mention whether consensus layer (CL) nodes should respond to these requests in a specific order.
Process Improvements for Ethereum Upgrades
- Upgrade Planning Process: Ethereum Foundation Protocol Support Lead Tim Beiko raised several process items to improve coordination for Ethereum upgrades. These included creating upgrade-specific folders under the Ethereum “pm” repository and the creation of a “Meta EIP” document to track the full scope of finalized network upgrades on Ethereum.
- Utility of Labelling Proposed Code Changes: Beiko also raised a question about the utility of labelling proposed code changes, Ethereum Improvement Proposals (EIPs), as “considered for inclusion” (CFI). The label has been used as a “soft signal” that an EIP author should continue work on a proposal for potential inclusion in a future hard fork.
Actionable Insights
- Consider the Implications of Networking Specifications: The discussion on clarifying specifications for the “BlockByRoot” and “BlobSidecarsByRoot” requests highlights the importance of clear and precise specifications in the development and operation of Ethereum. Stakeholders should consider the implications of these specifications on their operations and strategies.
- Monitor the Progress of Ethereum Upgrades: The ongoing testing and resolution of issues on Devnet #11 and Devnet #12 indicate that Ethereum upgrades are in progress. Stakeholders should monitor these developments to understand their potential impact on Ethereum’s performance and value.
- Understand the Importance of Process Improvements: The process improvements raised by Beiko, such as creating upgrade-specific folders and a “Meta EIP” document, underscore the importance of effective coordination and tracking in Ethereum upgrades. Stakeholders should understand these processes to better navigate Ethereum’s upgrade landscape.
