/bsc-snapshots

bsc-snapshots

Pruned database:

Asia Endpoint

geth-20211116.tar.gz

EU Endpoint

geth-20211116.tar.gz

US Endpoint

geth-20211116.tar.gz

MD5 checksum: 1bd9d6b5a9901d2f6930f14070189d60

Usage

Step 1: Preparation

  • Make sure your hardware meets the suggested requirement.
  • A disk with enough free storage, at least twice the size of the snapshot.

Step 2: Download && Uncompress

  • Copy the above snapshot URL.
  • Download: wget -O geth.tar.gz "<paste snapshot URL here>" . It will take one or two hours to download the snapshot, you can put it in the backgroud by nohup wget -O geth.tar.gz "<paste snapshot URL here?" &
  • Uncompress: tar zxvf geth.tar.gz or tar -I pigz -xvf geth.tar.gz. It will take more than two hours to uncompress. You can put it in the backgroud by nohup tar zxvf geth.tar.gz &
  • You can combine the above steps by running a script:
wget -O geth.tar.gz  "<paste snapshot URL here>"
tar zxvf geth.tar.gz
  • If you do not need to store the archive for use with other nodes, you may also extract it while downloading to save time and disk space:
wget -q -O - <snapshot URL> | tar -zxvf -

Step 3: Replace Data

  • First, stop the running bsc client if you have one by kill {pid}, and make sure the client has shut down.
  • Consider backing up the original data: mv ${BSC_DataDir}/geth/chaindata ${BSC_DataDir}/geth/chaindata_backup; mv ${BSC_DataDir}/geth/triecache ${BSC_DataDir}/geth/triecache_backup
  • Replace the data: mv server/data-seed/geth/chaindata ${BSC_DataDir}/geth/chaindata; mv server/data-seed/geth/triecache ${BSC_DataDir}/geth/triecache
  • Start the bsc client again and check the logs