Foresight News reports that Geth team developer @lightclients stated that starting today, all Ethereum execution clients support historical data pruning before the merge. For the mainnet, this means that the disk space required to run a node will decrease by 300-500 GB. Learn more about what this new feature means and how to take advantage of it. If you are a full node operator or validator, this change will not affect you except for saving space, as historical data is not needed to verify the head of the chain. Users and application developers of archive nodes who need historical data to generate custom indexes will need to start migrating to external historical data providers, which is the first step towards the complete expiration of the rolling historical data defined in EIP-4444.

#ETH