# Partial history expiry announcement

DevFeed: [Partial history expiry announcement](<https://devfeed.tech/articles/partial-history-expiry-announcement-17169.md>)

Original publisher: [Read original article](<https://blog.ethereum.org/en/2025/07/08/partial-history-exp>)

Author: Matt Garnett

Published: 2025-07-08T00:00:00Z

Content type: release

Language: en

Sources: [Ethereum Foundation Blog](<https://devfeed.tech/sources/ethereum-foundation-blog.md>)

Topics: [Ethereum](<https://devfeed.tech/topics/ethereum.md>), [Blockchain](<https://devfeed.tech/topics/blockchain.md>), [data](<https://devfeed.tech/topics/data.md>)

Tags: [announcement](<https://devfeed.tech/tags/announcement.md>), [blockchain](<https://devfeed.tech/tags/blockchain.md>), [disk-space](<https://devfeed.tech/tags/disk-space.md>), [ethereum](<https://devfeed.tech/tags/ethereum.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [protocol-announcements](<https://devfeed.tech/tags/protocol-announcements.md>), [snap](<https://devfeed.tech/tags/snap.md>), [space](<https://devfeed.tech/tags/space.md>), [storage](<https://devfeed.tech/tags/storage.md>)

## AI overview

Ethereum execution clients now support partial history expiry under EIP-4444. Removing block data from before the Merge can reduce the disk space required for an Ethereum node by 300-500 GB, while full rolling history expiry remains in development.

## Source excerpt

As of today, all Ethereum execution clients support partial history expiry in accordance with EIP-4444. While work on full, rolling history expiry is ongoing, users can expect to reduce the disk space required for an Ethereum node by 300-500 GB by removing the block data prior to the Merge. This...