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-04-25-07-01.tar.gz Wasabi S3 3.87 GiB 6c41d0e7dc06f15b4d24aa3754a5b996
blocks_bos_2019-04-24-19-01.tar.gz Wasabi S3 3.85 GiB 6050c9187e329c1cab7c71435ce1576d
blocks_bos_2019-04-24-07-01.tar.gz Wasabi S3 3.84 GiB 62f8841efd913b92804b042eca37985a
blocks_bos_2019-04-23-19-01.tar.gz Wasabi S3 3.83 GiB b88835ac33557696ca3faa4097dd2f9b
blocks_bos_2019-04-23-07-01.tar.gz Wasabi S3 3.81 GiB 09b8c11ffc4154062a753072740822ca
blocks_bos_2019-04-22-19-01.tar.gz Wasabi S3 3.8 GiB 7d55fc4811adca5a62dfa8422c789a51
blocks_bos_2019-04-22-07-01.tar.gz Wasabi S3 3.78 GiB 168a3e19306000968a6a684d6ecea37f
blocks_bos_2019-04-21-19-01.tar.gz Wasabi S3 3.76 GiB d52b7d8c2029e08006234a1fba03113a
blocks_bos_2019-04-21-07-01.tar.gz Wasabi S3 3.75 GiB cfc5b8ac7f5b6e68c35f38b6020d1d1c
blocks_bos_2019-04-20-19-01.tar.gz Wasabi S3 3.73 GiB 180a18dc4d9a3bc7ea15435789e22299
blocks_bos_2019-04-20-07-01.tar.gz Wasabi S3 3.71 GiB 0b6d74c7f313309e7bdbc9cb278f67c1
blocks_bos_2019-04-19-19-01.tar.gz Wasabi S3 3.69 GiB 5a7ce658022d1f8e17486090dd317c6e
blocks_bos_2019-04-19-07-01.tar.gz Wasabi S3 3.68 GiB 4cbc4155c6ebaaa671359c21e295c339
blocks_bos_2019-04-18-19-01.tar.gz Wasabi S3 3.66 GiB 45a555c014ecda4052bf5d3fcf38bba2
blocks_bos_2019-04-18-07-01.tar.gz Wasabi S3 3.64 GiB 42e43e0a2c4faf89f87b967eb82cf129

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 "https://eosnode.tools/api/blocks?network=bos&limit=1" -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
./start.sh --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.