Blockchain Snapshot 26th May 2021 - 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-05-31.tar.gz

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

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-05-31.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-05-31.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-05-26.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-05-26.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.

Can you help to figure out how to use the chaindata? I have removed my old chaindata data and start bor use the snapshot data. But the logs is error like below:

WARN [05-28|11:13:59.734] Synchronisation failed, dropping peer peer=317b056032dfea6693dd2682a3c54da4f0eafecc22a8e6da153b34919096402f err=“retrieved hash chain is invalid: invalid merkle root (remote: db6ab9df2f3c013abd913ff09600fdedb41a6cd8532c689c9c999dec2a88d233 local: 0e2d84da88b0bc5b392d04372ff13c14883bdd0d64dcb953af944330b6dc5764)”
ERROR[05-28|11:13:59.735] Ethereum peer removal failed peer=317b0560 err=“peer not registered”

I use followed blog to start matic

And my bor option is like below:

CMD ["./bor",
“–datadir”, “/data/matic”,
“–maxpeers”, “100”,
“–nousb”,
“–http”,
“–http.addr”, “0.0.0.0”,
“–http.api”, “eth,net,web3,txpool,bor”,
“–http.corsdomain=",
"–http.vhosts=
”,
“–bor.heimdall=http://heimdallr:1317”,
“–networkid”, “137”,
“–bootnodes”,
“enode://0cb82b395094ee4a2915e9714894627de9ed8498fb881cec6db7c65e8b9a5bd7f2f25cc84e71e89d0947e51c76e85d0847de848c7782b13c0255247a6758178c@44.232.55.71:30303,enode://88116f4295f5a31538ae409e4d44ad40d22e44ee9342869e7d68bdec55b0f83c1530355ce8b41fbec0928a7d75a5745d528450d30aec92066ab6ba1ee351d710@159.203.9.164:30303”]

done the init operation from mainnet genesis.json before

wget https://raw.githubusercontent.com/maticnetwork/launch/master/mainnet-v1/without-sentry/bor/genesis.json -O /data/matic/genesis.json
&& /app/bor --datadir /data/matic init /data/matic/genesis.json

Did you solve it? I have also been experiencing synchronization issues. my email: lpcheng360.li@gmail.com. pls contract me, thanks

hello,Did you solve it?

@delroy

WRT Heimdall: are you sure this is the from 31st May 2021? the last block seems to be ~5.2 million, which is from start of October 2020

So it’s 10million blocks out of date…

Edit: nvm, i mistoook the height for the block number

Any updates on this? I am experiencing similar sync issues. I am using a different snapshot though - the one of the 9th of June. It appears that bor is syncing only up to the snapshot. Any idea what might be causing it? Thanks

Actually latest block is ~12million, which is still from late March… 2 months before 26th May

Any more recent snapshot? this is taking weks to sync