Ethereum Merge Readiness: Client Testing and Consensus Layer Coordination
Summary
This account of Ethereum’s 95th Consensus Layer developer call describes the final coordination work ahead of the Merge, which was expected the following week. With many Merge-ready client releases already published, developers said node operators had become central to preparation. The Nimbus team planned a release addressing node performance and connectivity with execution-layer clients. Teku’s Mikhail Kalinin also reported progress on an optional test-vector suite for optimistic sync, intended to help client teams find bugs.
Other discussion covered connecting execution and consensus clients through the Engine API, checkpoint sync requirements, a final shadow fork, and plans to retire the Kiln test network after the Bellatrix upgrade. Developers also debated briefly suspending regular calls after the Merge to make time for rest and review of Shanghai proposals, including staked ETH withdrawals. The writeup records meeting updates and expectations rather than measured post-Merge outcomes; test adoption was optional, and the planned releases and call schedule were still subject to change.
Key ideas
- Merge preparation had shifted toward node operators as most client teams had already published ready software.
- Nimbus planned a release to address node performance and execution-client connectivity.
- An optional optimistic-sync test suite was being prepared to help client teams identify bugs.
- Developers discussed Engine API usability, checkpoint sync, test-network retirement and the timing of future calls.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.