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-02-23-07-00.tar.gz Wasabi S3 1.88 GiB b4f5d2cb5d59bbc0ec225c28df8371da
blocks_bos_2019-02-22-19-00.tar.gz Wasabi S3 1.86 GiB 99d8860a72401b8c9c3b29c7b71d4564
blocks_bos_2019-02-22-07-00.tar.gz Wasabi S3 1.84 GiB 648e656bba4e65bdf4f64ff34385c8f9
blocks_bos_2019-02-21-19-00.tar.gz Wasabi S3 1.82 GiB 32f95007792c0460e20b2a6425104a94
blocks_bos_2019-02-21-07-00.tar.gz Wasabi S3 1.79 GiB 18975761635c02d80b7d1526b25fcc44
blocks_bos_2019-02-20-19-00.tar.gz Wasabi S3 1.77 GiB 38ba244b9d021245f354812bdc7ee85f
blocks_bos_2019-02-20-07-00.tar.gz Wasabi S3 1.75 GiB 3a6722a3aab1e531cb08d72ba2a7596a
blocks_bos_2019-02-19-19-00.tar.gz Wasabi S3 1.73 GiB e86dd6a13c6155a849c79c69da9875dd
blocks_bos_2019-02-19-07-00.tar.gz Wasabi S3 1.7 GiB 34393c8d4958795faae0838b3084b121
blocks_bos_2019-02-18-19-00.tar.gz Wasabi S3 1.69 GiB b90052faece5fca74ed5b1f45ab8deaf
blocks_bos_2019-02-18-07-00.tar.gz Wasabi S3 1.67 GiB 292411fb85bb7992897b3d7794c0d845
blocks_bos_2019-02-17-19-00.tar.gz Wasabi S3 1.65 GiB bbed59b24054ca850bec23d89c3c940d
blocks_bos_2019-02-17-07-00.tar.gz Wasabi S3 1.62 GiB f32b8c0627d4920ff29a955efe7cdc07
blocks_bos_2019-02-16-19-00.tar.gz Wasabi S3 1.6 GiB 5e7083ce9de07af630dd99b181460f89
blocks_bos_2019-02-16-07-00.tar.gz Wasabi S3 1.58 GiB 38f87279eced293ac26a41225f9720e0

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.