EIP-4444 slashes Ethereum node sync time to under half a day
In brief
- EIP-4444 activated July 8, 2025, enables nodes to prune pre-Merge data and sync in under 12 hours
- Storage requirements drop 300–500 GB, allowing full nodes on 2 TB disks with aggressive settings
- All five major Ethereum execution clients support EIP-4444: Geth, Nethermind, Besu, Erigon, Reth
- Weak subjectivity checkpoints enable fast validation without storing full blockchain history
How EIP-4444 works
EIP-4444 introduces partial history expiry, a mechanism that lets nodes drop older data after a defined retention period of approximately 82,000 epochs, or about one year of history. Nodes validate the current chain head using weak subjectivity checkpoints, and the consensus layer can sync in minutes through checkpoint sync, eliminating the need to replay every block from genesis.
The change affects full nodes and validators, not archive nodes. Archive nodes will continue storing complete blockchain history for historical queries and indexing services.
Practical impact for operators
Prior to EIP-4444, a full node required more than 400 GB of disk space. Now, operators can run a fully functional node on a 2 TB disk with aggressive settings, keeping total storage under 0.5 TB. This means a consumer-grade machine with a decent SSD can participate in Ethereum's network—a significant shift from the hardware barrier that previously existed.
All five major Ethereum execution clients have shipped support: Geth v1.16.0, Nethermind 1.32.2, Besu 25.7.0, Erigon v3.0.12, and Reth v1.5.0. Coordinated rollout across the client ecosystem ensures network-wide stability and reduces fragmentation risk.
Part of Ethereum's larger roadmap
EIP-4444 sits within the "Purge" phase of Ethereum's roadmap, focused on reducing protocol complexity and node requirements. The upgrade doesn't discard historical data—it redistributes it. The Portal Network and other peer-to-peer data availability solutions are designed to fill this gap, ensuring that historical data remains accessible as nodes prune at different rates.
Lowering entry barriers for node operators strengthens Ethereum's decentralization. Fewer hardware constraints mean more participants can afford to run infrastructure, reducing reliance on a small set of well-capitalized providers.
Frequently asked questions
What does EIP-4444 do?
EIP-4444 enables Ethereum nodes to prune pre-Merge historical data after about one year, reducing storage from 400+ GB to under 0.5 TB. Nodes validate using weak subjectivity checkpoints instead of replaying all history, allowing new nodes to sync in under 12 hours.
Does EIP-4444 delete blockchain history permanently?
No. Archive nodes continue storing complete history. The Portal Network and peer-to-peer solutions ensure historical data remains accessible as full nodes prune at different rates. History is redistributed, not destroyed.
Which Ethereum clients support EIP-4444?
All five major execution clients have shipped support: Geth v1.16.0, Nethermind 1.32.2, Besu 25.7.0, Erigon v3.0.12, and Reth v1.5.0.
