Solia saysStatelessness lets clients verify blocks using witnesses that come with the block — no state database — paving the way for ultra-light Ethereum nodes once verkle trees ship.
Today every full node stores all of Ethereum's state — about 100 GB and growing. Statelessness turns that on its head: blocks carry witnesses (proofs of the state cells they touch), and verifiers check the block against the witnesses without needing the state. The current Merkle-Patricia trie makes witnesses too big to ship inline; verkle trees (bc-102) shrink them enough.
The payoff is a node that boots in minutes from any peer, holds kilobytes of RAM, and validates without a database. The trade-off is bandwidth: every block now carries hundreds of KB of witness data. The demo compares stateful storage to stateless witness traffic over a year.
Power-ups you unlock
Stateless clients verify blocks using witnesses instead of a state DB
Verkle trees are required to make witnesses small enough to ship inline
Storage is replaced by per-block witness bandwidth
Enables ultra-light, instantly-bootable nodes
On the Ethereum roadmap (the "Verge")
The Reentrancy Reaper attacks — common mistakes
Confusing statelessness with stateless transactions (different concept)
Underestimating the witness bandwidth that replaces storage
Assuming statelessness ships in the next hard fork (verkle migration first)
Forgetting block producers still need full state
Boss battleCompare stateful node storage (~100 GB growing) to stateless witness traffic per year and compute the trade-off.