Blockchain Snapshots June 16th

** Using snapshots while setting up full nodes help you sync faster without validating all data. This will speed up for setup dramatically. One can use this to sync faster instead of sync from scratch from other nodes since the Heimdall node sometimes takes days to sync.

Available snapshots

Heimdall : https://matic-blockchain-snapshots.s3.amazonaws.com/matic-mainnet/heimdall-fullnode-snapshot-2021-06-16.tar.gz

MD5sum: 6690a8882fa7dc7d1c8e11a1241308bc
Shasum: 6e886e116b7531dc06880b738076bb128bf8ebb5

Bor : https://matic-blockchain-snapshots.s3.amazonaws.com/matic-mainnet/bor-fullnode-snapshot-2021-06-16.tar.gz

MD5sum: 5fd1a60444b63285961fae59a40530fe
Shasum: c2b5753a2ba2d481524c2476ac40dda249f2b5ae

Using Snapshots

Heimdall

First, you need to set up your node with pre-requisites as per the node setup guide. Before you start services for Heimdall to sync, follow the below steps to use snapshot:

Download the Snapshot to your VM. To download the Snapshot Tar file to your VM you can run the following command

wget -c <Snapshot URL>

For example:

wget -c https://matic-blockchain-snapshots.s3.amazonaws.com/matic-mainnet/heimdall-fullnode-snapshot-2021-06-16.tar.gz

This will download the Snapshot of Heimdall.

Now, to unpack the Tar file in the Heimdall Data directory run the following command. You need to ensure that you’re running this command before you Start Heimdall service on your node. If your Heimdall service has started, please stop and then run the below command. Once unpacking is complete you can start the Heimdall service again.

tar -xzvf <snapshot file> -C <HEIMDALL_DATA_DIRECTORY>

For example:

tar -xzvf heimdall-fullnode-snapshot-2021-06-16.tar.gz -C ~/.heimdalld/data/

Note that if your Heimdall data directory is different then please mention that directory name correctly.

Bor

First, you need to set up your node with pre-requisites as per the node setup guide. Before you start services for Bor to sync, follow the below steps to use snapshot:

Download the Snapshot to your VM. To download the Snapshot Tar file to your VM you can run the following command

wget -c <Snapshot URL>

For example:

wget -c https://matic-blockchain-snapshots.s3.amazonaws.com/matic-mainnet/bor-fullnode-snapshot-2021-06-16.tar.gz

Now, to unpack the Tar file in the Bor Data directory run the following command. You need to ensure that you’re running this command before you Start Bor service on your node. If your Bor service has started, please stop and then run the below command. Once unpacking is complete you can start the Bor service again.

tar -xzvf <snapshot file> -C <BOR_DATA_DIRECTORY>

For example:

tar -xzvf bor-fullnode-snapshot-2021-06-16.tar.gz -C ~/.bor/data/bor/chaindata

Note that if your bor data directory is different then please mention that directory name correctly.

This is currently the latest Snapshot we have taken of the Blockchain stake. We will keep taking Snapshots every 2 weeks and keep posting this on the Forum and Discord Channels.**

Geth 1.10.x introduced offline state pruning, which required bor sync with the snapshot. My question is the bor snapshot you mentioned can be used for state pruning?

No, it is a different.
Snapshot in when discussing geth 1.10.x is the state of blockchain’s datastructure.
Snapshot in this thread’s context is just the state of heimdall/bor database.