IOTA Local Snapshots: New Features, Central Roadmap and Node Operator Details
New Features and Snapshots Available with IOTA, According to Developer Hans Moog
A new post on September 1st showed the IOTA platform’s development lately, discussing local snapshots. The tweet, which came from the official Twitter profile, read: “Hans Moog describes the concept of local snapshots, and the intricacies of implementing this feature.” The post then provides a link to the blog for IOTA, which is at https://blog.iota.org/.
The most recent blog, titled “Coming Up: Local Snapshots,” starts of by describing the activity on the network lately, which they credit to developers that are using their Tangle Technology. Though this helps with IOTA’s adoption, it also means that there will be bigger transactions on the nodes, which could slow them down.
Previously, the database operated with the use of global snapshots consistently, but it seems that these options are becoming less effective. The snapshots, as they presently are, puts a temporary stop on the coordinator as the developers go through the entire process. Then, the coordinator is forced to restart.
Local Snapshots will offer a solution that does not require so many cumbersome steps. As of September 1st, the company was testing out the implementation from within, and the blog commits to keeping the public informed during progress. Based on the company’s social media posts, it seems that this testing process is still underway.
Local Snapshots runs on the Tangle data structure. It allows users to find transactions, based on the recent history on the ledger. The blog provides this information about the “basic principle” of the Local Snapshots technology. It describes the “pruning of old transactions and persisting the balances,” offering this description of the process:
“We first choose a confirmed transaction that is sufficiently old and use this transaction as an ‘anchor’ for the local snapshot.
“We then prune all transactions that are directly or indirectly referenced by this transaction and clean up the database accordingly.”
“Before we clean the old transactions we check which balances were affected by them and persist the resulting state of the ledger in a local snapshot file, which is subsequently used by API as a new starting point.”
Basically, with the protocols in place, node operators will be able to sync snapshot files as new nodes show up within moments, and these nodes no long have a disk requirement. The process can be repeated to manage the space, but they do not require any other maintenance to complete the nodes, suing solid entry points.
To conclude this update for the IOTA community, the blog says,
“The upcoming feature of Local Snapshots will not just solve the space problems that arise with the growing adoption of IOTA but will also simplify the setup of new nodes and allow organizations and community members to operate permanodes. We will be opening this up for beta testing in the coming weeks. More information will be posted in the #snapshots channel on the IOTA Discord.”