Snapshot Guide


  1. First, you need to setup your node up with the pre-requisites as per the node setup guide

  2. Before you start your node for pundix to sync, follow the steps below to use snapshot

  3. If your pundix node has already started, please stop it and then follow the steps below to use the snapshot

  4. Once unpacking is complete, you can start the pundix service again

Types of PundiX Snapshots

  1. A pruned-snapshot, which contains only the most recent day's data

    • Only data for the most recent day, no earlier data

    • Small amount of data and footprint

  2. A full-node snapshot, which contains all the transaction data

    • Contains all transaction data, as well as current state data

    • Large amount of data and footprint

  3. An archive-snapshot, which contains all transaction data as well as all state data (syncing, not open yet)

    • Contains all transaction and status data

    • The amount of data is very large and takes up a lot of space

    • In general, you DO NOT need to use an archive node

The greater the blockchain data, the more evident the reduction is syncing time will be. If the current state of the blockchain will take about 2 days to sync, this method of syncing will reduce the time to sync by at least 12 hours.

Available snapshots

Snapshots are performed based on its type as per below, keeping a record of recent snapshot for as per below. If the date on the file is not yet updated and more than a week has lapsed since the last snapshot, you may replace the date in the file name to get the latest snapshot. If the date or day of the month are single digits, make sure to prepend a 0 in front of the single digit number. Date format will be in YYYY-MM-DD.

Downloading the Snapshots

Download the snapshot to your VM. To download the snapshot tar file to your VM you can run the following command:

wget -c

This will download the snapshot of pundix full-node data. Since it's full-node, downloading the snapshot and unpacking the file will take some time.

MD5 checksum for downloaded file

Checksums are often used to verify data integrity but are not relied upon to verify data authenticity, below are example of the md5sum command to check whether the file is downloaded correctly using

$ md5sum pundix-snapshot-mainnet-2023-01-01.tar.gz
4269fe416ca2d74d3925449f5ce7d214  pundix-snapshot-mainnet-2023-01-01.tar.gz

Compare the md5 hash against

Extracting the Snapshots

Now, to unpack the tar file in the PundiX Data directory run the following command:

tar -xzvf pundix-snapshot-mainnet-2023-01-01.tar.gz -C ~/.pundix/

If your pundix data directory is placed on different directory then please rename to that.

When you are unpacking the snapshot, it is already contained in a data folder, you will be replacing the data folder below. Be sure to maintain the integrity of this directory tree structure.

root@host:~# ls -l ~/.pundix/data/
total 64
drwxr-xr-x 2 root root 36864 Aug  2 16:49 application.db
drwxr-xr-x 2 root root  4096 Aug  2 16:26 blockstore.db
drwx------ 2 root root  4096 Aug  2 16:44 cs.wal
drwxr-xr-x 2 root root  4096 Aug  2 15:32 evidence.db
-rw------- 1 root root    46 Aug  1 10:02 priv_validator_state.json
drwxr-xr-x 3 root root  4096 Aug  1 10:02 snapshots
drwxr-xr-x 2 root root  4096 Aug  2 16:48 state.db
drwxr-xr-x 2 root root  4096 Aug  2 16:29 tx_index.db

Last updated