2021-04-15 snapshot (271 GB, md5sum 3ace16d3e2a52100025da387c73861a3f00de833)
2021-04-17 snapshot (260 GB, md5sum dd68c7fddaba42997eda013535a572cb)
March snapshot: download (146 GB, md5sum 74ada3bcd6a9d0f101501919f6cc8a534e9d796e)
February snapshot: download (87.4 GB, md5sum 6611dedde095ba9b72b50ebf6c35a8d7)
The following commands are step by step instructions for BSC node operators that can be used for two major use-cases:
- Fixing nodes that are stuck or crashed;
- Jumpstarting a newly setup validator node; avoid waiting some hours for synchronization
Basically, a compressed version of the last-known "good" chaindata is downloaded. Remove the node's old data and update it with the newly downloaded data. Finally, restart the sync-process from this known-good checkpoint.
Note: Ensure there is enough disk space for both the zip file AND its uncompressed contents. Double the space or more.
Download March Snapshot from CLI using wget
wget --no-check-certificate --no-proxy 'https://s3.ap-northeast-1.amazonaws.com/dex-bin.bnbstatic.com/s3-witness-data-download/chaindata_202103.zip?AWSAccessKeyId=AKIAYINE6SBQPUZDDRRO&Expires=1641450253&Signature=hOC8I8HSpCOytlYMVQwKRc5oUaI%3D'
Tip: extract the data in background
In case you can not wait for the extraction to finish, you can run it in the background
# Extract the data nohup unzip /NAME_OF_YOUR_HOME/node/geth/ -f chaindata_202102.zip & # Start your node back geth --config ./config.toml --datadir ./node --syncmode snap