How client diversity saved Holesky Lessons for the future

on YouTube ↗26m

" summary

Holesky hard-forks to Pectra and justifies an invalid deposit contract address causing three weeks of non-finality as a majority of validators follow the wrong chain; recovery relies on minority clients including the TypeScript consensus client Lodestar (≈2% of mainnet) blacklisting the invalid block root, adding a sync from unfinalized checkpoint API, and operators spinning up giant nodes (96 cores, ~755 GB RAM) and shared ENRs to bootstrap attestations — these tools and numbers drive whether the net recovers quickly.

AI-written summary · about

" chapters (10)

1. 0:00Introduction
2. 1:13What happened to Holesky
3. 3:19Client diversity importance
4. 5:11Problems during incident
5. 8:42Recovering minority chain
6. 13:19Finalizing chain risks
7. 16:10Client diversity prevented failure
8. 18:16Future improvements testing
9. 20:20Lessons learned
10. 20:42Q&A

" related talks

• 23mEthCC 2: Greg MarkouGreg Markou · EthCC[2]
• 27mThe Mauve RevolutionVitalik Buterin · Devcon 2
• 24mEthCC 2: Reto TrinklerReto Trinkler · EthCC[2]
• 16mManaging Risk With Institutional Staking on EthereumRok Kopp · TOKEN2049 Singapore 2023
• 28mVouch: Client Diversity without the DownsidesJim McDonald · Scaling Ethereum: The Merge Summit
• 38mPanel: Evolution of Ethereum ConsensusDanny Ryan, Trent Van Epps, Aftab Hossain · Scaling Ethereum: The Merge Summit
• 32mEthCC 2: Rob HabermeierRobert Habermeier · EthCC[2]
• 34mA Layman's Look at Staking on Ethereum Six Months After GenesisSuperphiz · Scaling Ethereum: The Merge Summit