Blocks Archive

Regular backups of the blocks data directory so you can fully sync with the BOS network.

Title Download Size MD5 Checksum
blocks_bos_2019-07-16-19-00.tar.gz Wasabi S3 6.14 GiB 63dd3027360161d8471e04699ed7ea13
blocks_bos_2019-07-16-07-00.tar.gz Wasabi S3 6.12 GiB c542745fdb66e7a933a5778caa519266
blocks_bos_2019-07-15-19-00.tar.gz Wasabi S3 6.11 GiB 5ef909a8a82bcc381f28a0123098e875
blocks_bos_2019-07-15-07-00.tar.gz Wasabi S3 6.1 GiB 7f9e158a8b29d653e9a2753fcd6d7c86
blocks_bos_2019-07-14-19-00.tar.gz Wasabi S3 6.08 GiB e83d4ade8effe52c664f62dd0f16a791
blocks_bos_2019-07-14-07-00.tar.gz Wasabi S3 6.07 GiB 5cee79c9e9a516f97633150f253a9cc7
blocks_bos_2019-07-13-19-00.tar.gz Wasabi S3 6.06 GiB 58ec26da38e37ac15ab2f6311b656a52
blocks_bos_2019-07-13-07-01.tar.gz Wasabi S3 6.04 GiB 959b2eb793b3f26321fbd664ff98b67d
blocks_bos_2019-07-12-19-00.tar.gz Wasabi S3 6.03 GiB 25d981b20b08c33eada30033bdc940a4
blocks_bos_2019-07-12-07-00.tar.gz Wasabi S3 6.02 GiB bfd428921d2b0d050df57b4b0596854a
blocks_bos_2019-07-11-19-00.tar.gz Wasabi S3 6 GiB 64b2fda85018d340ba2082be39e27d93
blocks_bos_2019-07-11-07-00.tar.gz Wasabi S3 5.99 GiB d601982bd6ce150c456a181f6b54253c
blocks_bos_2019-07-10-19-00.tar.gz Wasabi S3 5.98 GiB a81104f868c80eee8188d9d4861773df
blocks_bos_2019-07-10-07-01.tar.gz Wasabi S3 5.96 GiB 1775edb65024d37d29f910b93cdd71de
blocks_bos_2019-07-09-19-00.tar.gz Wasabi S3 5.95 GiB b028eaaaeaab9a3c494f98833ddea426
blocks_bos_2019-07-09-07-00.tar.gz Wasabi S3 5.94 GiB 36b0b21436bd121e259b6f8b3729c4cd

The blocks archives are taken daily from our bank of API nodes. These backups can be used across all node configurations and have been tested with Ubuntu, Centos and Debian.

How To Use

Download the archive, uncompress it into your data directory and start up nodeos requesting a hard replay which deletes the state database. This will validate the blocks, rebuild your state and sync with the live chain.

You can use the one-liner in the example to always download the latest backup. We also have a Blocks API which orders the archives in chronological order, newest first.

# Move to your local bos directory, removing the existing data directories (if relevant)
cd /opt/bos
rm -rf blocks state

# Download the latest blocks backup
wget $(wget --quiet "" -O- | jq -r '.data[0].s3') -O blocks_backup.tar.gz

# Uncompress to ./blocks
tar xvzf blocks_backup.tar.gz

# Start the chain and replay from the blocks backup
./ --hard-replay

# Tail the logs to watch the sync process
tail -f log.txt
2018-08-13T09:42:10.168 initializing chain plugin
2018-08-13T09:42:10.170 Hard replay requested: deleting state database
2018-08-13T09:42:10.171 Recovering Block Log...
2018-08-13T09:42:10.171 Moved existing blocks directory to backup location: '/mnt/blocks-2018-08-13T09:42:10.171'
2018-08-13T09:42:10.172 Reconstructing '/mnt/blocks/blocks.log' from backed up block log
2018-08-13T09:44:33.490 Existing block log was undamaged. Recovered all irreversible blocks up to block number 10887835.
2018-08-13T09:44:33.493 Reversible blocks database was not corrupted. Copying from backup to blocks directory.
2018-08-13T09:44:38.833 Log is nonempty
2018-08-13T09:44:38.833 Index is empty
2018-08-13T09:44:38.833 Reconstructing Block Log Index...
2018-08-13T09:47:12.722 No head block in fork db, perhaps we need to replay
2018-08-13T09:47:12.722 Initializing new blockchain with genesis state
2018-08-13T09:47:12.755 existing block log, attempting to replay 10887835 blocks
    140700 of 10887835

How Long To Replay?

Once you kick off the hard-replay, the sync will take hours. Exactly how long is dependent on your system configuration. The replay process is mostly CPU bound, as nodeos is single threaded the important factor is your CPU clock speed, not the overall number of cores.

When you replay, you should follow the nodeos log. The code snippet on the left shows you an example of the log messages that you should see when you execute the hard-replay. After the initial validation you get a progress output to give you a better indication of the time it will take.