All Ethereum Execution Clients now support historical data pruning before the merge, reducing storage capacity for nodes from 300 to 500 GB.
This does not interrupt the operation of full nodes and validators, but archive node users or application developers need to seek external historical data sources to ensure full access to information.
MAIN CONTENT
Ethereum implements the 'expiration of historical data' mechanism according to EIP-4444 to optimize memory.
Storage capacity for Ethereum nodes is reduced from 300 to 500 GB without affecting operation.
Archive node users must switch to external historical data providers.
What is Ethereum Execution Client and what does supporting historical data pruning mean?
The official blog of the Ethereum Foundation, the execution client is responsible for processing transactions and network state. Supporting historical data pruning before the merge helps reduce storage pressure on the node's disk by up to 500 GB.
This is the first step in applying the historical data expiration mechanism, as defined in EIP-4444, thereby improving performance and operational costs of the Ethereum mainnet.
How does historical data pruning affect the operation of full nodes and validators?
A representative of the Ethereum Foundation stated that pruning only affects storage memory, not the transaction processing and block validation operations of full nodes and validators.
This optimization is necessary to reduce storage capacity, helping the number of nodes running on the Ethereum network remain stable and improve performance.
Vitalik Buterin, Co-founder of Ethereum, stated in 2024
Therefore, full nodes still operate smoothly and transparently with the Proof of Stake (PoS) consensus mechanism currently in use.
What should archive node users and application developers do with this change?
Archive nodes store all historical blockchain data, including previous states. When this data is pruned, users need to switch to external data providers that can access the full history.
The list of endpoints providing historical data is updated by the Ethereum community at https://eth-clients.github.io/history-endpoints/ to ensure information retrieval capabilities for application development and on-chain analysis.
To maintain the sustainable and efficient development of the Ethereum ecosystem, using external historical data services is a necessary step for many developers and organizations.
Joseph Lubin, Founder of ConsenSys, 2024
What is EIP-4444 and its importance in upgrading the Ethereum network?
EIP-4444 proposes to regulate the 'expiration of historical data' so that execution clients can remove pre-merge data after a certain period.
As a result, Ethereum nodes require less storage capacity, helping reduce costs, encouraging users to operate nodes, and enhancing security according to the decentralized model. This is an important upgrade contributing to expanding storage capacity and optimizing the infrastructure of the Ethereum blockchain network.
Comparison table between before and after applying pruning according to EIP-4444
Criteria Before Pruning After Pruning Node Storage Capacity Over 3 TB (depends on client, full historical data) Save 300 – 500 GB, significant reduction in capacity Impact on full nodes and validators No reduction in storage capacity No impact on performance, only memory optimization Dependency on external data No need for external providers Archive node users need to use external historical services.
Frequently Asked Questions
What is historical data pruning? Pruning is the process of removing old blockchain data to reduce storage capacity without affecting node operation. How does pruning affect the security of the Ethereum network? It does not affect security, as full nodes and validators still maintain all the necessary state for the consensus mechanism. What should users of archive nodes do after pruning is applied? They need to use external historical data service providers to access complete historical information. Is EIP-4444 an important upgrade for the Ethereum network? Yes, it helps improve storage efficiency, save operational costs, and increase scalability for the system. What is the address to access historical data endpoints after pruning? Information at https://eth-clients.github.io/history-endpoints/ is officially provided by the Ethereum community.
Source: https://tintucbitcoin.com/ethereum-client-giam-dung-luong-luu-tru/
Thank you for reading this article!
Please Like, Comment, and Follow TinTucBitcoin to stay updated on the latest news about the cryptocurrency market and not miss any important information!