Ethereum’s Nethermind Client to Delete Historical Records for Disk Space Savings

Ethereum’s Nethermind client is preparing for a major update scheduled for May 1st, with the primary goal of freeing up disk space by deleting historical records. This initiative is part of a broader effort to enhance the performance and efficiency of the Ethereum network. The update will target older, less critical data that is no longer essential for the current state of the blockchain, thereby reducing the storage demands on nodes running the Nethermind client.
The synchronization process for a Nethermind node to the latest block and network state involves various modes, each with distinct speeds, storage requirements, and trust assumptions. Snap sync, for example, allows a node to perform the initial synchronization and download of the network state up to 10 times faster than fast sync. This mode is typically enabled by default for networks that support it and can be configured with the Sync.SnapSync option. However, it is important to note that snap sync should not be enabled on a previously synced node, as it is designed solely for first-time synchronization.
Fast sync, on the other hand, enables a node to respond to queries about the current state of accounts and token holdings. This mode involves multiple stages, including the synchronization of block headers and state data. The pivot block number is used to enhance performance, and the synchronization process involves downloading block data and state tree nodes. The speed of state sync is crucial, as a slow network or file system can result in repeated downloads of tree parts, leading to inefficiencies.
Archive sync is the most storage-intensive and slowest sync mode, capable of answering queries about historical states, such as account balances from two years ago. This mode stores all historical data, making it the most demanding in terms of storage. The sync process for archive sync can take several days for the Ethereum Mainnet, depending on the speed of the disk and network connection. During this process, nodes may experience varying download and processing speeds, with the current and average speeds being displayed in the logs.
The update on May 1st will primarily affect nodes running in archive sync mode, as it will delete historical records that are no longer necessary for the current state of the blockchain. This will free up significant disk space, making it easier for nodes to maintain synchronization with the network. However, it is important to note that this update may affect the ability of nodes to answer historical queries, as the deleted data will no longer be available.
In summary, the upcoming update to Ethereum’s Nethermind client on May 1st is a strategic move to optimize disk space usage by deleting historical records. This update will primarily impact nodes running in archive sync mode, freeing up storage and improving synchronization efficiency. While this change may limit the ability to query historical data, it is a necessary step to ensure the long-term sustainability and performance of the Ethereum network.

Comments
No comments yet