Following the activation of EIP-4444 on July 8, 2025, Ethereum execution clients can now prune historical data created before the Merge — the network's September 2022 transition to proof of stake — cutting storage requirements by 300 to 500 GB and enabling new nodes to sync in under half a day. With aggressive settings, operators can run a fully functional node on a 2 TB disk while keeping total storage below 0.5 TB.

What EIP-4444 actually changes

The improvement centers on what is known as “partial history expiry.” Rather than requiring every node to store the complete history of the Ethereum blockchain, EIP-4444 allows nodes to drop older data after a defined retention period. The initial design specified roughly 33,000 epochs — each a 6.4-minute unit of consensus time — a figure later revised to approximately 82,000 epochs, or about one year of history.

Validation of the current chain head relies on weak subjectivity checkpoints recent states that clients take from a trusted source instead of verifying the entire chain from genesis. The consensus layer can come online within minutes through checkpoint sync, while the execution layer no longer needs to download and verify a decade of transaction receipts. For operators who require archival access, historical data retrieval mechanisms remain available as an optional feature.

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 each include the necessary flags and configurations.

Why storage was becoming a problem

Prior to EIP-4444, a full node needed more than 400 GB of disk space, and that figure was moving in only one direction. Every new block, every smart contract interaction, and every token transfer added to the pile.

An important distinction applies: the change affects full nodes and validators, not archive nodes. Archive nodes, which serve historical queries for block explorers and analytics platforms, will continue storing everything.

The accessibility equation

A sub-half-day sync on under 0.5 TB of storage means a relatively modest consumer-grade machine with a decent SSD can participate in Ethereum’s network. For operators, that translates into verifying transactions and balances on their own hardware rather than relying on third-party providers. That stands in contrast to the multi-day sync processes and terabyte-plus storage demands that previously greeted new node operators.

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.

The remaining question is how the network handles the transition period as nodes begin pruning at different rates and historical data becomes distributed rather than universally replicated. The Portal Network and other peer-to-peer data availability solutions are designed to fill this gap, ensuring that historical queries can still be resolved even when most nodes have moved on.

Source: CryptoBriefing