Ethereum Activated EIP-4444 to Shrink Node Storage
The July 2025 update reduces storage demands by up to 500 GB, enabling faster network synchronization.
Updated on Sept. 26, 2026 in Cybersecurity
Live Poll
Should blockchain networks prioritize lowering hardware requirements to increase user participation?
On July 8, 2025, the Ethereum network activated EIP-4444 to allow execution clients to prune historical data older than one year. This change significantly lowers hardware barriers for running a full node by reducing required storage capacity.
Why it matters
Reducing storage overhead decreases the technical barrier to entry for node operators, thereby supporting network decentralization. The change streamlines protocol complexity by offloading the requirement to maintain the entire chain history from every node.
Full nodes can now operate on a 2 TB disk using less than 0.5 TB of storage, down from the higher overhead required before the EIP-4444 implementation. The update limits data retention to approximately 82,000 epochs, or one year.
The players
Ethereum
A decentralized open-source blockchain platform that supports smart contracts and an ecosystem of distributed applications.
The details
The implementation allows Ethereum execution clients—software that processes transactions and updates the ledger state—to drop historical data once it exceeds the one-year threshold. Nodes now validate the chain head using weak subjectivity checkpoints, which are trust-minimized markers that allow nodes to sync without verifying every block from genesis. While standard nodes prune this older data to save space, archive nodes continue to store the complete historical record.
Timeline
July 8, 2025: The Ethereum network officially activated EIP-4444.
The Tech Race
This activation marks a specific milestone in the Ethereum Foundation's roadmap to manage protocol complexity and hardware demands. It follows a multi-year effort by core developers to align network maintenance requirements with modern infrastructure capabilities.
Node operators can now sync new instances in under half a day, a significant improvement over previous synchronization times. Those looking to support the network on standard consumer hardware can now do so with significantly reduced storage commitments.
The takeaway
The move to prune historical data reflects a shift toward prioritizing node accessibility as the blockchain continues to grow. Developers and node operators should monitor the performance of the five supported execution clients to ensure stability under the new retention limits.
Further reading
For broader context on how network protocols manage data integrity and node requirements, visit Cybersecurity.
Live Poll
Should blockchain networks prioritize lowering hardware requirements to increase user participation?
