🤔 Need blocks and a snapshot? Use the bundle API to always get the latest compatible backups.

Mainnet Snapshots

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

Title Download Size MD5 Checksum
snap_2019-12-08-02-00.tar.gz Wasabi S3 556.18 MiB fbd7b17e3d03407cc86685c1e236628c
snap_2019-12-08-01-00.tar.gz Wasabi S3 556.17 MiB 53c43f4fa03c4be47904b95422af35dd
snap_2019-12-08-00-00.tar.gz Wasabi S3 556.07 MiB c44cef59b1a71d7c5081627875fb7d96
snap_2019-12-07-23-00.tar.gz Wasabi S3 556.09 MiB 9b57e69c6b74430c0451f8d107eee2fd
snap_2019-12-07-22-00.tar.gz Wasabi S3 556.16 MiB 9af6f3c1707454b428d5f167ebfd706e
snap_2019-12-07-21-00.tar.gz Wasabi S3 556.27 MiB b5491f137b35b02b0c0713e6d86a62c4
snap_2019-12-07-20-00.tar.gz Wasabi S3 556.31 MiB 9c12384e33045ea8eb489ce58b33df6f
snap_2019-12-07-19-00.tar.gz Wasabi S3 556.28 MiB 11f83bb5636ed4a35cad6308072c087c
snap_2019-12-07-18-00.tar.gz Wasabi S3 556.29 MiB 5f17b5ed451a7f970dd0fad83f57789f
snap_2019-12-07-17-00.tar.gz Wasabi S3 556.32 MiB 2e1e6afacf85ad68ca7f144315b2e63a
snap_2019-12-07-16-00.tar.gz Wasabi S3 556.17 MiB 67d4ffcd5c519bbab9f407e26f59808d
snap_2019-12-07-15-00.tar.gz Wasabi S3 556.06 MiB cc3f2a88ee7f17559e4f7a30c33208c8
snap_2019-12-07-14-00.tar.gz Wasabi S3 556.04 MiB 610541fd37184d2456b8bb388409213c
snap_2019-12-07-13-00.tar.gz Wasabi S3 556.06 MiB 9f1501d6d84ee27ef85a3d70585148cb
snap_2019-12-07-12-00.tar.gz Wasabi S3 555.86 MiB 932c27656c5aa7cfa5d35db15ef2de83
snap_2019-12-07-11-00.tar.gz Wasabi S3 555.93 MiB 9bfa863e5af162dd9d53493223e59489
snap_2019-12-07-10-00.tar.gz Wasabi S3 555.95 MiB 0cc5cb66e80b339c17bf2c86a41a04ed
snap_2019-12-07-09-00.tar.gz Wasabi S3 555.99 MiB 9c63d30f96d22d4ad573700ac40c402a
snap_2019-12-07-08-00.tar.gz Wasabi S3 555.83 MiB d28196b40e47fc7cee7a8e7e7cb96b53
snap_2019-12-07-07-00.tar.gz Wasabi S3 555.84 MiB 317e765b1645fd13797f7d095eb1a18d
snap_2019-12-07-06-00.tar.gz Wasabi S3 555.78 MiB 9db5876b57760a24083ed4889eb8110c
snap_2019-12-07-05-00.tar.gz Wasabi S3 555.63 MiB 07bc52ff055197e23ddb33ce7c42ffa4
snap_2019-12-07-04-00.tar.gz Wasabi S3 555.49 MiB 696e1c07354b97b33d2c40b87cb92410
snap_2019-12-07-03-00.tar.gz Wasabi S3 555.09 MiB bf8e9fd1a3eb9e82211ee139d4de06e6
snap_2019-12-07-02-00.tar.gz Wasabi S3 554.92 MiB 26b00ebab1aa4dffc106ba8528b499e3
snap_2019-12-07-01-00.tar.gz Wasabi S3 554.66 MiB f9e18a6d9af37f42ebe3d350421b45c6
snap_2019-12-07-00-00.tar.gz Wasabi S3 554.66 MiB 294545714e7dace1c6b668bce42a7987

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 head block referenced in the snapshot.

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 "https://eosnode.tools/api/snapshots?limit=1" -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
./start.sh --snapshot "$(ls -t snapshots/*.bin | head -n1)"

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