Statelessness eliminates state bloat. Full nodes today must store the entire Ethereum state, a requirement that centralizes hardware and throttles throughput. Stateless clients verify blocks using cryptographic proofs, not local state storage.
the-ethereum-roadmap-merge-surge-verge
Blog
Why Statelessness is Ethereum's True Endgame
The Merge and Surge were warm-ups. The Verge's stateless client model is the final, definitive unlock for infinite scalability and true decentralization. This is how removing the state barrier changes everything.
introduction
THE SCALING IMPERATIVE
Introduction
Statelessness is the only viable path to scaling Ethereum's consensus layer without compromising decentralization.
Verkle Trees enable this transition. They replace Ethereum's Merkle Patricia Tries, providing the small, constant-sized proofs required for stateless validation. This is a prerequisite for scaling block gas limits without exploding node requirements.
The endgame is a rollup-centric, stateless L1. A stateless Ethereum foundation supports thousands of high-throughput rollups like Arbitrum and zkSync, while preserving permissionless node operation. The current model of state growth is unsustainable for global adoption.
key-trends
WHY STATELESSNESS IS THE ENDGAME
The State of the State: The Core Bottleneck
Ethereum's current state growth is unsustainable, creating a fundamental bottleneck for decentralization, security, and scalability. Statelessness is the only viable path forward.
01
The Problem: Unbounded State Growth
Every new account and smart contract permanently bloats the global state, forcing node operators to buy more expensive hardware. This centralizes the network.
- State size grows ~50 GB/year, requiring >2 TB SSDs for archive nodes.
- Full sync time can exceed 2 weeks, a massive barrier to new validators.
- This is a direct attack on Ethereum's core value proposition: credible neutrality through decentralization.
>2 TB
Archive Node Size
~50 GB/yr
Growth Rate
02
The Solution: Verkle Trees & Witnesses
Replace the Merkle Patricia Trie with Verkle Trees, enabling stateless clients. Nodes no longer need to store the full state; they verify execution using compact cryptographic proofs called witnesses.
- Witness size target: ~250 KB per block vs. GBs of state today.
- Enables light clients with full security guarantees, not just trust assumptions.
- Paves the way for single-slot finality by removing state I/O as a bottleneck for consensus.
~250 KB
Target Witness Size
>1000x
Proof Efficiency Gain
03
The Enabler: History Expiry (EIP-4444)
Even with statelessness, historical data grows forever. EIP-4444 mandates clients to stop serving historical data older than one year, outsourcing it to decentralized networks like Portal Network or BitTorrent.
- Reduces node storage requirements by ~90% after the first year.
- Shifts the paradigm: Ethereum becomes a live state machine, not a permanent archive.
- Forces the ecosystem to build robust, decentralized history storage layers.
-90%
Storage Reduction
1 Year
Retention Period
04
The Consequence: Supercharged Rollups
Statelessness is the final piece for truly scalable L2s. Sequencers become stateless execution engines, drastically reducing their operational overhead and cost.
- Enables massively parallel execution without state contention.
- zkRollups (Starknet, zkSync) can generate proofs for cheaper, smaller state transitions.
- Optimistic Rollups (Arbitrum, Optimism) can sync new nodes in minutes, not days, enhancing decentralization.
Minutes
L2 Node Sync
10x+
Throughput Potential
05
The Bottleneck: Proposer-Builder Separation (PBS)
Stateless validators are fragile to MEV. Without PBS, builders could DOS validators with blocks containing invalid transactions, forcing expensive re-execution. PBS is a prerequisite.
- Builders (specialized, stateful) construct full blocks with validity proofs.
- Proposers (stateless validators) simply verify the proof and sign.
- Protocols like MEV-Boost are the crude prototype; enshrined PBS is the final form.
Required
For Stateless Val.
$1B+
Annual MEV Market
06
The Timeline: A Decade-Long Migration
This isn't a single upgrade; it's a multi-year architectural migration. The roadmap is The Verge -> The Purge -> The Splurge.
- The Verge (Verkle Trees): Enables statelessness. Likely 2025/2026.
- The Purge (EIP-4444): Limits history. Likely 2026+.
- The Splurge: All other improvements (PBS, Account Abstraction). Ongoing.
- The goal: A network where running a node is as easy as running a light client today.
2025-2026
Verkle ETA
Multi-Year
Full Migration
THE STATE COST BOTTLENECK
The Node Participation Crisis: By The Numbers
Comparing the hardware and operational requirements for running a full node under current and proposed Ethereum execution models. Statelessness is the only path to sustainable decentralization.
| Node Requirement | Current Stateful (Post-Merge) | Verkle Trees (Prague/Electra) | Full Stateless (Endgame) |
|---|---|---|---|
State Growth per Year | ~150 GB | ~150 GB | 0 GB |
SSD Storage Required | 2+ TB (High I/O) | 2+ TB (High I/O) | 500 GB (Low I/O) |
RAM Recommended | 16-32 GB | 16-32 GB | 8-16 GB |
Sync Time (Full Archive) | ~2 weeks | ~1 week | < 1 day |
Bandwidth per Month | ~5 TB | ~5 TB | < 1 TB |
Requires State Pruning | |||
Witness Size per Block | N/A | ~1-2 MB | < 250 KB |
Hardware Cost (Est.) | $1,500+ | $1,200+ | $500 |
deep-dive
THE STATE CRISIS
Verkle Trees & Stateless Clients: The Technical Unpacking
Statelessness solves Ethereum's existential scaling bottleneck by decoupling execution from state storage.
Statelessness is the endgame because it eliminates the primary constraint on node operation: massive, ever-growing state storage. This enables light clients to verify execution with minimal data, a prerequisite for true scalability.
Verkle Trees replace Merkle Patricia Tries. They use vector commitments to shrink proofs from ~300 KB to ~150 bytes. This makes witness data small enough for network transmission.
Clients no longer store state. Instead, they receive a compact witness with each block, proving the state changes. This shifts the storage burden away from consensus participants.
Evidence: The current Ethereum state is ~1 TB. A Verkle proof for a complex Uniswap swap is ~1-2 KB, versus megabytes today. This enables mobile client verification.
counter-argument
THE BOTTLENECK
The Steelman: "But Rollups Already Scale Ethereum!"
Rollups are a scaling stopgap that merely relocates the state growth problem to a higher layer.
Rollups export state growth. They compress execution but still require full nodes to download and verify their ever-expanding state. This shifts the data availability burden to Ethereum, creating a long-term L1 consensus bottleneck.
Statelessness is the prerequisite. Without verifiable state expiry via EIP-4444 and Verkle trees, even rollup-centric scaling hits a wall. The current model is unsustainable for mass adoption.
The evidence is in the data. An Arbitrum full node today requires ~1.5TB of storage. Without statelessness, this grows linearly with usage, centralizing node operation and undermining Ethereum's decentralization guarantee.
takeaways
BEYOND SCALING
The Endgame Implications
Statelessness isn't just about throughput; it's a fundamental re-architecture that redefines the roles of nodes, validators, and users.
01
The Problem: The State Bloat Death Spiral
Ethereum's full state grows by ~50 GB/year, forcing node requirements up and centralizing network participation. This is unsustainable for a global settlement layer.
- Rising Barriers: Node sync times stretch to weeks, pricing out hobbyists.
- Centralization Pressure: Only entities with petabyte-scale infrastructure can run full nodes long-term.
- Security Risk: Fewer verifiers means weaker guarantees of state correctness.
>1 TB
State Size
+50 GB/Yr
Growth Rate
02
The Solution: Verkle Trees & Witnesses
Replace Merkle Patricia Tries with Verkle Trees, enabling stateless clients. Validators no longer store the full state; they verify compact cryptographic proofs (witnesses).
- Constant-Size Proofs: Witness size is ~150 bytes vs. MBs for current proofs.
- Stateless Validators: Run a node with near-zero storage, only needing the latest block header.
- Enables Light Clients: Mobile and browser wallets can become first-class verifiers.
~150 B
Witness Size
~1s
Verify Time
03
The Architectural Shift: Separating Execution from Verification
Statelessness finalizes Ethereum's transition to a verification-centric model, mirroring trends in zk-rollups like zkSync and StarkNet.
- Pure Validity Proofs: The network consensus verifies state transitions, not recomputes them.
- Unlocks Parallel EVMs: Execution clients like Monad and Sei can propose blocks without global state access.
- Paves Way for SNARKed L1: Enables a future where the Ethereum L1 itself is secured by succinct proofs.
1000x
Verifier Scale
zkEVM
Alignment
04
The Economic Endgame: Ultra-Light Infrastructure
Drastically lowers the cost to participate in consensus, flipping the economic model of node operation and staking.
- Home Staking Viable: Run a validator on a Raspberry Pi with an external block builder.
- Killer App for PBS: Proposer-Builder Separation becomes mandatory, creating robust markets for MEV distribution.
- Global Verification: Enables trust-minimized bridges and oracles to run their own light clients.
-99%
Node Cost
10M+
Potential Nodes
05
The Client Diversity Catalyst
Eliminates the biggest barrier to new execution and consensus client development, breaking the Geth hegemony.
- Reduced Dev Burden: New clients like Erigon or Reth don't need complex state management.
- Faster Innovation: Experimental features (e.g., new precompiles, VMs) can be tested without forking the entire state.
- Resilience: A bug in one client's state logic no longer risks a chain split, as verification is unified.
>5
Major Clients
0%
Geth Dominance Goal
06
The Privacy Paradox: Stateless but Accountable
Statelessness, combined with zk-SNARKs, enables private transactions on a public ledger without burdening the network with data bloat.
- Stealth Addresses: Can be verified via a witness without storing recipient mapping.
- ZK Rollup Synergy: Protocols like Aztec become native extensions, not second-layer hacks.
- Regulatory Clarity: The base layer verifies compliance proofs, not private data, aligning with initiatives like Vitalik's "Privacy Pools".
zk-SNARK
Tech Enabler
Full Audit
Capability
ENQUIRY
Get In Touch
today.
Our experts will offer a free quote and a 30min call to discuss your project.
NDA Protected
Confidentiality24h Response
Time to ValueDirectly to Engineering Team
No Sales Fluff10+
Protocols Shipped
$20M+
TVL Overall