Mainnet Snapshots

Hourly snapshots of the EOS mainnet so you can instantly sync with the network.

Title Download Size MD5 Checksum
snap_2019-01-21-12-00.tar.gz Wasabi S3 281.12 MiB 30e3c00064b66ee09a5d6a75a30b1519
snap_2019-01-21-11-00.tar.gz Wasabi S3 280.84 MiB fc5b2b1cc1de1211337245bed99ee5bf
snap_2019-01-21-10-00.tar.gz Wasabi S3 280.25 MiB fb09afb7d3b1486e9687dbcca0238ec8
snap_2019-01-21-09-00.tar.gz Wasabi S3 279.72 MiB 2a01674d795ddf10c4a1863c49c84d85
snap_2019-01-21-08-00.tar.gz Wasabi S3 279.25 MiB d86411ea6625c5ee1536a5bfafa33b62
snap_2019-01-21-07-00.tar.gz Wasabi S3 279.04 MiB f11854fec6728d9cabf62aefb69057b7
snap_2019-01-21-06-00.tar.gz Wasabi S3 279.28 MiB 53ee5cd69aef7accdb0f82645c8149e9
snap_2019-01-21-05-00.tar.gz Wasabi S3 279.31 MiB 5bb4d3a74c868081305613e197571ac5
snap_2019-01-21-04-00.tar.gz Wasabi S3 279.82 MiB 5a23e70e39b106ccdea756c655653346
snap_2019-01-21-03-00.tar.gz Wasabi S3 280.4 MiB 3bb80782e4c5918515150c0a532224b5
snap_2019-01-21-02-00.tar.gz Wasabi S3 280.47 MiB d9df1fa6cbceedcea29080cb6f0228f8
snap_2019-01-21-01-00.tar.gz Wasabi S3 281.17 MiB d6c799682e1cbd9ac046db234630a49f
snap_2019-01-21-00-00.tar.gz Wasabi S3 281.49 MiB 5b287f6645f10b2d9e937c2bc4811d62
snap_2019-01-20-23-00.tar.gz Wasabi S3 281.33 MiB 6a3e009e7fbcd6c671ce58c69d2d23df
snap_2019-01-20-22-00.tar.gz Wasabi S3 281.2 MiB fbc1f1bfc5ce7ccdc9f4955ddf20bd16
snap_2019-01-20-21-00.tar.gz Wasabi S3 281.08 MiB 2a87ac0cd7c3fa7665689babbdd01f9b
snap_2019-01-20-20-00.tar.gz Wasabi S3 281.05 MiB 1fecf137d5bf9c2f4dfc907300f0b59f
snap_2019-01-20-19-00.tar.gz Wasabi S3 280.79 MiB 2868dfd454a2fd4e0be8220dde0e20ec
snap_2019-01-20-18-00.tar.gz Wasabi S3 280.91 MiB 91eedd2d498ee089878db472a3b6e173
snap_2019-01-20-17-00.tar.gz Wasabi S3 280.96 MiB 9a69bd4e03ce5ee5236cbf8f1ba90a16
snap_2019-01-20-16-00.tar.gz Wasabi S3 281.19 MiB bde10406f1ce152b2c0eb859b353128f
snap_2019-01-20-15-00.tar.gz Wasabi S3 280.54 MiB 61c4a61971bbe7ec193cb1dd65af68be
snap_2019-01-20-14-00.tar.gz Wasabi S3 280.24 MiB 3d89b6870e7c303eb8e3b7a188fde69e
snap_2019-01-20-13-00.tar.gz Wasabi S3 279.93 MiB 98a9ba2f8a667ea548dfd6a612912f29
snap_2019-01-20-12-00.tar.gz Wasabi S3 279.83 MiB 9f2f25bd8df994745c7e8562450eda5b
snap_2019-01-20-11-00.tar.gz Wasabi S3 279.84 MiB 1ba5c6cc4b43e141c7cb2bda062d52e7
snap_2019-01-20-10-00.tar.gz Wasabi S3 279.53 MiB 4cd062fdcc9b4c6a712e6f23b54e9e6f
snap_2019-01-20-09-00.tar.gz Wasabi S3 279.45 MiB 7818587e1ca54659e4289e684a9125ec
snap_2019-01-20-08-00.tar.gz Wasabi S3 279.05 MiB fbf8a2e976bb042ad71b36436a4ce03d
snap_2019-01-20-07-00.tar.gz Wasabi S3 278.64 MiB f9a57bf99b57f058e441fbd4644ae235
snap_2019-01-20-06-00.tar.gz Wasabi S3 278.44 MiB 51cd77c26cd687bf0092be99ba2c8521
snap_2019-01-20-05-00.tar.gz Wasabi S3 278.15 MiB 31aac71ad48a927fd9ad71e17a831745
snap_2019-01-20-04-00.tar.gz Wasabi S3 277.87 MiB df02f5a0885010d8424eb47136aa6705
snap_2019-01-20-03-00.tar.gz Wasabi S3 277.52 MiB 15b32a855951a9efce76c1309d0c8cce
snap_2019-01-20-02-00.tar.gz Wasabi S3 277.6 MiB 15d8fc5897ff0131909298110242a74e
snap_2019-01-20-01-00.tar.gz Wasabi S3 277.66 MiB 8e1f6bd2456ba7bc586d6088e309350b
snap_2019-01-20-00-00.tar.gz Wasabi S3 277.64 MiB 083dcf1cebec2df697bb12a8e2937968

These snapshots are platform agnostic and taken from our own cluster of API nodes.
They can be used with or without a blocks log.

Using Snapshots

This is a great way to get synced to the network within a minute, you can see the original notes on Github. There are a couple of points to be aware of:

  • The snapshots contain all the consensus state required to bootstrap a node at a given head block, so there's no need for long replays to build state from the blocks log.
  • This sync method is intended for producing nodes, however if you don't intend on supporting history data, it will work perfectly for API/full nodes.

What's The Catch?

After being accustomed to long replay times via Block backups, the near instant snapshot sync seems like magic. But the magic comes at a cost:

  • If you want to support retrospective chain data via the RPC API or P2P, then you must provide a blocks log that contains blocks up to the snapshotted block. The blocks log may contain additional blocks, they will be applied as part of the startup process.
  • These snapshots do not support any plugins, so this doesn't support history data.

How To Use

First, you must do some preparation. Remove the state directory if it exists, then you need to make a decision. If you want to support old chain data, then you must have a blocks directory with a block log containing data up to, or past the snapshotted block.

Download the snapshot, uncompress it and start nodeos with the snapshot flag pointing to the absolute location of the fresh snapshot.

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 snapshot. We also have a Snapshots API which orders the archives in chronological order, newest first.

# Move to your local eos directory, removing the existing state directory (if relevant)
cd /opt/mainnet
rm -rf state

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

# Uncompress
tar xvzf snapshot.tar.gz

# Start the chain and sync from the provided snapshot
./ --snapshot "snapshots/$(ls -t snapshots/*.bin | head -n1)"

# Tail the logs to watch the sync in all its glory
tail -f log.txt