Verkle Trees & Statelessness

The State Keeps Growing

Every account balance, smart-contract's code, and stored value on a blockchain lives in its 'state' — a giant, constantly-growing database that full nodes must keep to validate new blocks. As a chain is used for years, this state balloons, and storing and accessing it becomes a heavier and heavier burden. That matters for decentralisation: if running a node requires ever more disk, memory, and fast storage, fewer people can afford to run one, and the network concentrates into the hands of well-resourced operators. Managing state growth is one of the quiet but fundamental long-term challenges of keeping a blockchain both scalable and decentralised.

Statelessness: Verify Without Storing

The vision of 'statelessness' is that a node could verify a new block without storing the entire state itself. Instead, each block would come with small cryptographic 'witnesses' — proofs that the specific bits of state a block touches really have the values claimed. A stateless verifier checks the block against these witnesses rather than against a local copy of everything, so it no longer needs terabytes of state on hand. This would dramatically lower the hardware bar for participating in verification, letting far more people and devices help secure the network. Verkle trees are the key piece of cryptography that makes those witnesses small enough to be practical.

• State is the ever-growing database of balances, code, and storage a node must keep
• Growing state raises node hardware costs, threatening decentralisation
• Statelessness = verifying blocks using small witnesses instead of storing all state
• Verkle trees make those witnesses small enough to ship with every block