|blocks_2019-01-21-07-01.tar.gz||Wasabi S3||103.11 GiB||45fcacf4fb9f30369b854113149ccdb7|
|blocks_2019-01-20-07-02.tar.gz||Wasabi S3||102.57 GiB||19abf4a2e3cc46576bacc88bdd27fce5|
|blocks_2019-01-19-07-01.tar.gz||Wasabi S3||101.97 GiB||1e9eedf199d88e56fdb18978a174031c|
|blocks_2019-01-18-07-01.tar.gz||Wasabi S3||101.32 GiB||5e4fdf49354e4db40af549fb655d0817|
|blocks_2019-01-17-07-01.tar.gz||Wasabi S3||100.66 GiB||663d273f859c2156d3516f62d684f217|
|blocks_2019-01-16-22-36.tar.gz||Wasabi S3||100.45 GiB||f17a8824412428df9d5fe511d962e5f0|
|blocks_2019-01-16-07-01.tar.gz||Wasabi S3||100.08 GiB||fd141067b7b6be353ba7d387bba5d0e0|
|blocks_2019-01-15-07-01.tar.gz||Wasabi S3||99.48 GiB||d772eda745a099a1f898f681b571b125|
|blocks_2019-01-14-07-01.tar.gz||Wasabi S3||98.87 GiB||ab74711776385786441c561e6f0563d7|
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.
The example assumes you have used our automation framework to install and configure the EOS application. It includes handy bash helpers to auto dameonise the nodeos process and capture all output into a single log file.
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 eos directory, removing the existing data directories (if relevant) cd /opt/mainnet rm -rf blocks state # Download the latest blocks backup wget $(wget --quiet "https://eosnode.tools/api/blocks?limit=1" -O- | jq -r '.data.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 --wasm-runtime wabt # 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.