Blockchain State Expiry: Why Networks Cannot Store Everything

Blockchains are incredible at making a shared record nobody can quietly rewrite. They’re terrible at being a free, eternal database. That tension is finally catching up.

If every token, allowance, airdrop, NFT, and abandoned contract lives forever, state balloons. Nodes get heavier. Fewer people can run them. Fees reflect that pressure. And at some point, the network has to say no.

That’s where “state expiry” comes in. Not a silver bullet, not an overnight switch. Just a set of strategies that say: the chain keeps the most important stuff accessible, and the rest needs proofs, snapshots, or a fresh touch to stick around.

Point Details State growth is compounding Measured weekly new Ethereum state rose from roughly 105 MiB to ~326 MiB after gas limit increases, or about 116 GiB per year of extra state pressure (HackMD — Week 2). Expiry vs history pruning History expiry drops old block bodies and receipts. State expiry targets long-lived account and storage entries. Different goals, different risks. Tiering helps today A prototype showed about 58% of trie nodes moved cold and an observed ~21.6% total storage reduction, shrinking the hot trie near 60% (HackMD — EPF notes). UTXO-style payments on Ethereum Research suggests native UTXOs for one-shot payments could cut permanent state for those flows by about 99.8% (Ethereum Research (ethresear.ch)). Builders have levers now Transient storage, logs over storage, batch patterns, and state-light designs reduce footprint even before protocol-level expiry lands. User experience must not break Expiry needs renewals or proofs so balances, allowances, and NFTs are still usable without scaring normal users.

… Continue reading the full article at the original source below.