Blockchain Snapshots June 9th - Full Node

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-09.tar.gz

MD5sum: 72867b8911ce995d1bc50c452c0da768
Shasum: c20a08a1f8c7167b5c98fce7f6333f821c965612

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

MD5sum: 7c760c048da04e7c4dfe967514b1ae89
Shasum: cc9300f97dd78b808c75fbf8ac95a401f629cd34

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-09.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-09.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-09.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-09.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.

I am using this snapshot however Bor cannot be fully sync. I believe it is sync up to the snapshot point

{“jsonrpc”:“2.0”,“id”:“curltext”,“result”:{“currentBlock”:“0xec9abf”,“highestBlock”:“0xf04961”,“knownStates”:“0x0”,“pulledStates”:“0x0”,“startingBlock”:“0xec9ad7”}}

Any idea on what might be causing this and how it can be resolved?

Thanks

me too, help!!! I’m going crazy

Not sure what might be causing this problem. The snapshot is only to ensure that your nodes don’t need to sync from scratch so that you get a headstart.

These snapshots have been tested thoroughly and only then published.

I know that might not be related to the image, but I will post this here in case you or someone else faced similar issue.

My logs look like:
INFO [06-17|08:56:33.118] Retrying again in 5 seconds for next Heimdall span path=clerk/event-record/list
INFO [06-17|08:56:43.119] Retrying again in 5 seconds for next Heimdall span path=clerk/event-record/list
WARN [06-17|08:56:50.634] Served miner_setEtherbase conn=195.123.222.16:42188 reqid=1 t=“16.357µs” err=“the method miner_setEtherbase does not exist/is not available”
INFO [06-17|08:56:53.121] Retrying again in 5 seconds for next Heimdall span path=clerk/event-record/list
INFO [06-17|08:57:03.122] Retrying again in 5 seconds for next Heimdall span path=clerk/event-record/list
INFO [06-17|08:57:13.123] Retrying again in 5 seconds for next Heimdall span path=clerk/event-record/list
INFO [06-17|08:57:23.124] Retrying again in 5 seconds for next Heimdall span path=clerk/event-record/list
INFO [06-17|08:57:33.126] Retrying again in 5 seconds for next Heimdall span path=clerk/event-record/list
INFO [06-17|08:57:43.127] Retrying again in 5 seconds for next Heimdall span path=clerk/event-record/list

I suspect this might be related to some port not configured properly… Do you know what’s the meaning of those logs?

1 Like

@Aris Please check your heimdalld sync status. If it is synced completely, then check the status of heimdalld-rest-server.

curl localhost:1317/bor/span/10

i got this problem :slight_smile:

Synchronisation failed, dropping peer peer=b95c878ee72b264f044e926a7e0af80817b035f938ee069574f4f535e028b5ee err=“retrieved hash chain is invalid: invalid merkle root (remote: 70cdb53669ccf754c7cbac2790f9928549a2d769760fb89b8f258192c0df522c local: 4b78f8ef97a26416b49e5baa3d845af754a0084a6f2fb164f56c166b36424eaa)”

Jul 23 05:22:43 ip-172-26-208-42 bash[11295]: ERROR[07-23|05:22:43.901] Ethereum peer removal failed peer=5a9be195 err=“peer not registered”

please help me . .