Mainnet Snapshots

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

Title Download Size MD5 Checksum
snap_2018-12-19-09-00.tar.gz Wasabi S3 230.67 MiB 8da399185ec02a0748cb01777b8ddc5c
snap_2018-12-19-07-00.tar.gz Wasabi S3 230.23 MiB 535daf4cc67a72d6bf44ed0d35fc2526
snap_2018-12-19-06-00.tar.gz Wasabi S3 229.82 MiB c7aa9f6746722c0ffe9eb47239a36cc3
snap_2018-12-19-05-00.tar.gz Wasabi S3 229.88 MiB df1d4d84cc6b5c141ca56e5283b17a55
snap_2018-12-19-04-00.tar.gz Wasabi S3 229.25 MiB 45869546e08cec6e559e2e661c6e015e
snap_2018-12-19-03-00.tar.gz Wasabi S3 228.58 MiB dc2a51429fbe7205697a84edf5de772e
snap_2018-12-19-02-00.tar.gz Wasabi S3 228.2 MiB 7eb547b9f5c67d20648d0f6a9b6f45fc
snap_2018-12-19-01-00.tar.gz Wasabi S3 227.88 MiB a453042ac81ac3c28537d488aea78a93
snap_2018-12-19-00-00.tar.gz Wasabi S3 228.21 MiB 0caf9cebd073f5f9dd7db2970d6d4b86
snap_2018-12-18-23-00.tar.gz Wasabi S3 227.5 MiB fa91593553670f1db456bcbb7944f128
snap_2018-12-18-22-00.tar.gz Wasabi S3 227.28 MiB bb4ed489e7a766dc27799f72bf280ea3
snap_2018-12-18-21-00.tar.gz Wasabi S3 226.89 MiB 837cfbcff323825c93b74ededf71831d
snap_2018-12-18-20-00.tar.gz Wasabi S3 227.16 MiB 6d7927daf8d32a94a9b2384a8fa90a6c
snap_2018-12-18-19-00.tar.gz Wasabi S3 226.83 MiB d354f8b3bc4f9b43070a4e692d76cf51
snap_2018-12-18-18-00.tar.gz Wasabi S3 226.21 MiB 0d7252e6dc4e53581d58f61e0ca3c738
snap_2018-12-18-17-00.tar.gz Wasabi S3 226.37 MiB 3bf12319fb95bad52f65cd770054da20
snap_2018-12-18-16-00.tar.gz Wasabi S3 226.74 MiB 9cc5cbc3c229ef30a6bc3b20137f023c
snap_2018-12-18-15-00.tar.gz Wasabi S3 226.93 MiB de9c2ecedda42baf67d431e25f1307f3
snap_2018-12-18-14-00.tar.gz Wasabi S3 226.94 MiB 336bf0b35bdc01edeaa3eb9b4e89b4c1
snap_2018-12-18-13-00.tar.gz Wasabi S3 227.13 MiB 8f7c29d1007cfe526c07bc5f0c8cd0bf
snap_2018-12-18-12-00.tar.gz Wasabi S3 226.78 MiB ee5314a7ebdb514c071f216314329f95
snap_2018-12-18-11-00.tar.gz Wasabi S3 226.64 MiB 773fad0ac2007a2b5f6de9a0fea1372f
snap_2018-12-18-10-00.tar.gz Wasabi S3 226.37 MiB 5e2bc36fc25313726e1a00f5b6538dc9
snap_2018-12-18-09-00.tar.gz Wasabi S3 226.34 MiB dfeaf4b587bbdc262f4c6f5f607fe82a
snap_2018-12-18-07-00.tar.gz Wasabi S3 226.09 MiB 3d9934474670c75df8508cbb64f8f8a2
snap_2018-12-18-06-00.tar.gz Wasabi S3 225.96 MiB d029b40429044947b74807958465632b
snap_2018-12-18-05-00.tar.gz Wasabi S3 225.9 MiB e3c067e5235aa8c42ee9488a8b8f1920
snap_2018-12-18-04-00.tar.gz Wasabi S3 225.91 MiB cd891533274c5ac93e71228a6ad7f705
snap_2018-12-18-03-00.tar.gz Wasabi S3 225.91 MiB 523b270d922909e0264c851181960f92
snap_2018-12-18-02-00.tar.gz Wasabi S3 225.66 MiB af7232ab8cc704772ddfb38b8c6215d8
snap_2018-12-18-01-00.tar.gz Wasabi S3 225.45 MiB 1d0bb6dd06038033b4544d267b929d89
snap_2018-12-18-00-00.tar.gz Wasabi S3 225.32 MiB 73a9c615c9d8760d1522361750e70331

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 to ./snapshots
tar xvzf snapshot.tar.gz

# Start the chain and sync from the provided snapshot
./ --snapshot $(tar -ztf snapshot.tar.gz)

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