Ethereum Consensus Developers Test the Merge and Discuss Validator Exits
Summary
Ethereum consensus layer developers reviewed preparations for the proof-of-stake Merge, client software work, and possible specification changes. A shadow fork tested combinations of consensus and execution clients, including scenarios where clients were paused before activation to check whether they could resynchronize. Early results reported that all tested combinations reached the Merge and stayed in sync, with 97% validator participation; the report says the offline validators were affected by an unrelated client issue.
The meeting also covered the planned Ropsten testnet fork and uncertainty about its terminal total difficulty, leaving the timing decision for a later meeting. Client teams described work on message propagation, memory use, proposer-builder interfaces, light clients, and threshold signatures. Research discussion focused on removing an unused data parameter and giving withdrawal-key holders a way to initiate validator exits, a concern for delegated staking. These were developer updates and preliminary test results, not a final account of the shadow fork or settled protocol decisions; several topics remained under discussion.
Key ideas
- A multi-client shadow fork tested Merge behavior and recovery after clients were paused.
- Early results reported successful transitions across tested client combinations and 97% validator participation.
- The Ropsten activation timing depended on revisiting the testnet’s terminal total difficulty.
- Client teams reported work spanning propagation, memory use, external block building, and light clients.
- Developers discussed enabling withdrawal-key holders to initiate exits from delegated validators.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.