Chain Data Snapshots
Last updated
Last updated
For a node to join the network and work with other nodes, it must sync data with other nodes first. Overtime, the data to be synchronized will increased and the process will take several days to weeks, even months.
The snapshot consists of 2 parts that must be downloaded and extracted for a node to synchronize properly.
TomoX:
Chain Data:
We also have checksum information to verify downloaded files are correct.
TomoX:
Chain Data:
TomoX: https://snapshot.viction.xyz/archive-node/TOMOX_DATA.tar.zst
Chain Data: https://snapshot.viction.xyz/archive-node/CHAIN_DATA.tar.zst
We also have checksum information to verify downloaded files are correct.
TomoX: https://snapshot.viction.xyz/archive-node/TOMOX_DATA.tar.zst.sha1
Chain Data: https://snapshot.viction.xyz/archive-node/CHAIN_DATA.tar.zst.sha1
At the time of this writing, the size of the snapshot files are:
Nearly 800GB for the Full Node
Nearly 3.5TB for the Archive Node
Please make sure that you have enough free space to store the files and the extracted contents.
This example demonstrates how to use the snapshot files with the assumption that the node has been stopped and node data is stored at the following path: /var/lib/docker/volumes/viction_mainnet/_data/data
The file CHAIN_DATA.tar.zst is huge at the time of writing and will take a long time to download and extract. You can use the following command to perform those operations in background:
This example demonstrates how to use the snapshot files with the assumption that the node has been stopped and node data is stored at the following path: /var/lib/docker/volumes/viction_mainnet/_data/data
The file CHAIN_DATA.tar.zst is huge at the time of writing and will take a long time to download and extract. You can use the following command to perform those operations in background: