Ethereum Developers Separate Withdrawals From Proto-Danksharding
Summary
Ethereum developers agreed to prioritize staked ETH withdrawals for the Shanghai upgrade and pursue proto-danksharding separately, because EIP 4844 was considered less ready and combining the work could delay withdrawals. The call covered progress on multi-client test networks and a proposal to bound validator scans during withdrawal processing to a maximum of 1,024 validators. Developers planned further testing of that proposal and discussed unresolved blob synchronization questions for EIP 4844.
Other topics included peer discovery and IPv6 support, reducing reliance on a single checkpoint sync tool, distributed validator support, and changes to Engine API documentation. The call also addressed conflicting estimates of Ethereum client distribution, with the chair favoring stake-based data over crawler results. This is a dated account of developer coordination and research discussion, rather than a trading analysis or evaluation of whether the proposed changes would succeed. Several implementation details remained open at the time of the call.
Key ideas
- Developers chose to advance staked ETH withdrawals independently of EIP 4844 to avoid delaying the Shanghai upgrade.
- A proposed bounded sweep would cap the validator scan for withdrawals at 1,024 validators.
- Developers were testing withdrawals across multiple execution and consensus clients, with broader client coverage still pending.
- The call covered research and specification topics including blob syncing, checkpoint sync diversity, distributed validators, and Engine API documentation.
- The chair considered stake-based client distribution estimates more reliable than crawler-based estimates.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.