Solia saysEIP-4444 lets execution clients drop historical blocks older than ~1 year — old data lives on the portal network — keeping the node footprint flat as the chain grows.
Ethereum history grows endlessly: every block ever produced sits on every full node by default. EIP-4444 proposes that execution clients expire history older than one year, dropping those blocks from disk. State and recent history stay; ancient blocks are served by archival nodes and the decentralized portal network.
The result is a runnable node footprint that stays roughly flat instead of growing ~80 GB per year. Anyone who needs old data can fetch it from peers that opt in to serving it. The demo projects disk usage with and without history expiry over a decade.
Power-ups you unlock
Clients drop history older than ~1 year (EIP-4444)
Old blocks served by the portal network / archive nodes
Keeps node disk footprint flat instead of growing ~80 GB / year
State stays — only block bodies are expired
Part of the "Purge" track on the roadmap
The Reentrancy Reaper attacks — common mistakes
Confusing history expiry with state expiry (different proposals)
Assuming nobody can read old blocks — the portal network serves them
Treating EIP-4444 as already shipped (it is in progress)
Forgetting that archive needs still exist (just not at every node)
Boss battleProject disk usage over 10 years with and without EIP-4444 history expiry, given ~80 GB/year growth.