What Happens After the Merge
summary
Roadmap after the Merge focuses on concrete protocol changes: a post-merge cleanup fork removes eth1 voting, enables withdrawals, and migrates execution data to SSZ with a later transaction-format upgrade; scaling adds ~64 data shards (250–512 KB shards every 12s) secured initially by committees and then by data availability sampling using polynomial commitments (recoverable from half the pieces); consensus improvements include single-secret leader election, VDFs and proof-of-custody; state management combines state expiry + statelessness and a ~400-gas per 32B code-access rule.
AI-written summary · about
chapters (21)
- 0:00Intro
- 2:11Roadmap
- 3:38Postmerge cleanup fork
- 10:05Sharding
- 16:16Security Improvements
- 17:36Address Extension
- 18:51State Size
- 26:32Expired States
- 29:22Account Abstraction
- 31:22EVM Improvements
- 31:59CBDC Casper
- 33:42Starking Everything
- 36:30The Future
- 40:32Zoom
- 40:42State Expiry
- 44:34Technical Debt
- 46:53Layer 3 Defined
- 50:14Async Interaction
- 51:37Positive Effects
- 53:19Snarks
- 55:35Random Ideas
