🤔 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-06-18-20-00.tar.gz Wasabi S3 445.77 MiB 7730c6700826b13b055edc37ba868a12
snap_2019-06-18-19-00.tar.gz Wasabi S3 445.79 MiB 018c9b32e876e4d10d74b0f951a92813
snap_2019-06-18-18-00.tar.gz Wasabi S3 445.76 MiB ceb48a1ace76524198c19af33ee4fada
snap_2019-06-18-17-00.tar.gz Wasabi S3 445.81 MiB 7fe9ff89b08d21cc6702690a19c37474
snap_2019-06-18-16-00.tar.gz Wasabi S3 445.83 MiB 65177c4ea82c9bd49acf88c23263b064
snap_2019-06-18-15-00.tar.gz Wasabi S3 445.88 MiB 1622542c5b4d39967f57e86906a9abdc
snap_2019-06-18-14-00.tar.gz Wasabi S3 445.78 MiB ceb5c490cc75523a8217a9d953517030
snap_2019-06-18-13-00.tar.gz Wasabi S3 445.93 MiB a2eea69d4967abc9f0ad95ec0f91bfa7
snap_2019-06-18-12-00.tar.gz Wasabi S3 446.26 MiB a18bb9959056aed8c270a916180c5c22
snap_2019-06-18-11-00.tar.gz Wasabi S3 446.74 MiB 90421d7296c8b5c9175dee78a6af3ea7
snap_2019-06-18-10-00.tar.gz Wasabi S3 447.04 MiB 56fa24b66e25502a940dadbe21bdfdd2
snap_2019-06-18-09-00.tar.gz Wasabi S3 447.4 MiB 93372db59280f7c12a759db6c0d92cb4
snap_2019-06-18-08-00.tar.gz Wasabi S3 447.66 MiB 3de94902ed69e8fa068f4443a9c62a89
snap_2019-06-18-07-00.tar.gz Wasabi S3 447.77 MiB c3946c53a78ddf3ff392942083001267
snap_2019-06-18-06-00.tar.gz Wasabi S3 448.02 MiB bc4cc3a1915b58bf7fd8f36b9300e34a
snap_2019-06-18-05-00.tar.gz Wasabi S3 448.23 MiB 948267d7caa52a48b128610ce1992b0d
snap_2019-06-18-04-00.tar.gz Wasabi S3 448.32 MiB 7448063215fe3c57e32d0b4eac3b4d75
snap_2019-06-18-03-00.tar.gz Wasabi S3 448.24 MiB e9ca3e62f793412a74d6f0b4d871277e
snap_2019-06-18-02-00.tar.gz Wasabi S3 448.15 MiB 061c7f5037380b844e2690990a0ea14a
snap_2019-06-18-01-00.tar.gz Wasabi S3 448.3 MiB 74ceb1cbf41899d17d6e27eead334604
snap_2019-06-18-00-00.tar.gz Wasabi S3 448.69 MiB acbcce19bb7d635e23969b2f2e78a956
snap_2019-06-17-23-00.tar.gz Wasabi S3 448.76 MiB c0a6be7ab5530fedfda8a9b39446f97b
snap_2019-06-17-22-00.tar.gz Wasabi S3 448.84 MiB 2a5ccec2b7014e19504d6dae677ab6b2
snap_2019-06-17-21-00.tar.gz Wasabi S3 448.77 MiB 4e972c109ae0a01f10b6ad01c1c6b25b
snap_2019-06-17-20-00.tar.gz Wasabi S3 448.74 MiB 59cd4363703725c8a51abb28e97b7b62
snap_2019-06-17-19-00.tar.gz Wasabi S3 448.74 MiB 57b409c093fa7b25418e5ffa91be5aab
snap_2019-06-17-18-00.tar.gz Wasabi S3 448.63 MiB b13abdf7e6681cbe15a5329ddd4ee63b
snap_2019-06-17-17-00.tar.gz Wasabi S3 448.65 MiB a3081416f85147a647af8558746c99da
snap_2019-06-17-16-00.tar.gz Wasabi S3 448.64 MiB 098c740706f8cba7c7064925339e591b
snap_2019-06-17-15-00.tar.gz Wasabi S3 448.56 MiB 09b6b3c68551d78ef063f008786aa9b5
snap_2019-06-17-14-00.tar.gz Wasabi S3 448.56 MiB 1c58524dd97d1d95b5bad1d3dc2860f3
snap_2019-06-17-13-00.tar.gz Wasabi S3 448.5 MiB bf99cec306fff319f8f4d7fd2f1dba97
snap_2019-06-17-12-00.tar.gz Wasabi S3 448.34 MiB 7c55627e36a2a6094dd79835ec5be521
snap_2019-06-17-11-00.tar.gz Wasabi S3 448.45 MiB f113d1064f5a08742686c991f7c0e2fe
snap_2019-06-17-10-00.tar.gz Wasabi S3 448.45 MiB 310fb607ba0ca3e25cdac0c4c698f03c
snap_2019-06-17-09-00.tar.gz Wasabi S3 448.44 MiB 53c6ad92637d7fb0bc638010089f0d7b
snap_2019-06-17-08-00.tar.gz Wasabi S3 448.41 MiB cdc79c3d9d5d6bc2732de8430544df18
snap_2019-06-17-07-00.tar.gz Wasabi S3 448.13 MiB c20800584f14678f858c6e9da4d4cfd9
snap_2019-06-17-06-00.tar.gz Wasabi S3 448.12 MiB 812202cdcd3ba1c0cd2cf9bc9c61cb69
snap_2019-06-17-05-00.tar.gz Wasabi S3 448.02 MiB 772ec3907546753cddfec900de86084b
snap_2019-06-17-04-00.tar.gz Wasabi S3 448.16 MiB 17593f7ecd4ae8ff2a7a064141db7749
snap_2019-06-17-03-00.tar.gz Wasabi S3 448.08 MiB d032a853283837f3a4cebbef47175f95
snap_2019-06-17-02-00.tar.gz Wasabi S3 448.12 MiB 5052691e5049e96e167ede516333acbb
snap_2019-06-17-01-00.tar.gz Wasabi S3 448.13 MiB 5f1dd6db3f836ca33567446d151b3ba9
snap_2019-06-17-00-00.tar.gz Wasabi S3 448.58 MiB b63338fcd13806f2ad36f08145bd4849

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