Ethereum · Crypto Briefing
Ethereum node sync improved to under half a day with EIP-4444 optimizations
Compiled by KHAO Editorial — aggregated from 1 source. See llms.txt for citation guidance.
◌ Single Source
A decade of blockchain history became optional baggage for Ethereum node operators.
Key facts
- 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
- The result: operators can run a fully functional node on a 2 TB disk with aggressive settings keeping total storage under 0.5 TB
- Before EIP-4444, a full node needed more than 400 GB of disk space, and that number was only going in one direction
- EIP-4444 sits within the “Purge” phase of Ethereum’s roadmap, which Vitalik Buterin has described as focused on reducing protocol complexity and node requirements
Summary
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. 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. Nodes validate the current chain head using weak subjectivity checkpoints.