Research Summary
The report discusses the Ethereum All Core Developers Consensus Call #124, where developers discussed the progress of the Cancun/Deneb upgrade on Devnet #12, rules on slashable message propagation, and the call schedule for the upcoming weeks. The developers are on track to launch a Goerli shadow fork testing the Cancun/Deneb upgrade with all clients in the next one to two weeks.
Key Takeaways
Progress on Devnet #12
- Onboarding of all EL/CL client combinations: All execution layer (EL) and consensus layer (CL) client combinations, including the Prysm client, have been onboarded to Devnet #12. However, client combinations with Prysm have not yet been tested with MEV-Boost.
- Testing of MEV workflow: The MEV workflow is being tested across the other CL clients on Devnet #12. The Lighthouse client has been recently patched to address a bug related to MEV.
- Issue with Besu node: An issue with a Besu node on Devnet #12 was noticed, and the root cause is still being identified.
Slashable Message Updates
- Introduction of new events to Beacon Chain API: A pull request was created to add new events to the Beacon Chain API that will allow node operators to learn about slashable events more quickly. This is especially useful in the case of high volumes of slashable messages.
- Measuring block propagation times: Due to the Cancun/Deneb upgrade and the introduction of blob transactions, measuring block propagation times will become more difficult. Developers are considering extending existing relevant Beacon Chain API events with a timestamp field.
- Gossip conditions for blobs: Developers discussed the gossip conditions for blobs, noting that the existing rules lead to unexpected consequences. They recommended considering changes to clarify the rules on how to handle the propagation of slashable messages in a future upgrade.
Minor Change to Libp2p Networking Protocol
- Introduction of “IDONTWANT” control message: A minor change to the libp2p networking protocol was discussed to reduce the amplification of large messages. A new “IDONTWANT” control message can be used to notify libp2p peers to suspend sending back large messages.
ACD Holiday Call Schedule
- Informal meeting on December 28th: Developers discussed the possibility of an informal meeting on December 28th to discuss progress on Cancun/Deneb. The Monday testing call on the 25th has been cancelled.
Actionable Insights
- Monitor the progress of Devnet #12: Stakeholders should keep an eye on the progress of Devnet #12, especially the testing of MEV workflow and the resolution of the issue with the Besu node.
- Understand the implications of slashable message updates: It’s crucial to understand the implications of the new events added to the Beacon Chain API and the changes in measuring block propagation times.
- Stay updated on the changes to libp2p networking protocol: Stakeholders should stay updated on the changes to the libp2p networking protocol, especially the introduction of the “IDONTWANT” control message.
