Ethereum node sync improved to under half a day with EIP-4444 optimizations

With the activation of EIP-4444 on July 8, 2025, Ethereum execution clients can now prune pre-Merge historical data, slashing storage requirements by 300 to 500 GB and enabling new nodes to sync in under half a day. The result: operators can run a fully functional node on a 2 TB disk with aggressive settings keeping total storage under 0.5 TB. What EIP-4444 actually changes EIP-4444 introduces what’s called “partial history expiry.” Instead of requiring every node to store the complete history of the Ethereum blockchain, nodes can now drop older data after a defined retention period. The initial design specified roughly 33,000 epochs, but this was revised to approximately 82,000 epochs, or about one year of history. Nodes validate the current chain head using weak subjectivity checkpoints. The consensus layer can sync in minutes through checkpoint sync, while the execution layer benefits from not needing to download and verify a decade of transaction receipts. Historical data retrieval mechanisms remain available as an optional feature for operators who need archival access. All five major Ethereum execution clients have shipped support. Geth v1.16.0, Nethermind 1.32.2, Besu 25.7.0...