Ethereum clients support historical data pruning, reducing node storage requirements by 300-500 GB
Powered by ChatGPTGeth team developer @lightclients posted that, starting today, all Ethereum execution clients support historical record pruning of pre-merge data. For the mainnet, this means that the disk space required to run a node will be reduced by 300-500 GB. To learn more about what this new feature means and how to take advantage of it, this change will not affect you if you are a full node operator or validator, other than saving space, as historical records are not required to verify the head of the chain. Archive node users and application developers who need historical records to generate custom indexes need to start migrating to external historical record providers, which is the first step towards the full rolling history expiration defined in EIP-4444. [Foresight News]