🤔 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-11-15-23-00.tar.gz Wasabi S3 549.32 MiB c3b1db46323be3dc1770130c9ca85ad9
snap_2019-11-15-22-00.tar.gz Wasabi S3 549.32 MiB 8ae4310a8efe7699d08ab07b43c53608
snap_2019-11-15-21-00.tar.gz Wasabi S3 549.34 MiB 9eaa1e82d36eea86fd80ed48228f3b10
snap_2019-11-15-20-00.tar.gz Wasabi S3 549.39 MiB 0eb558eaaa2e8c3f3076129f32b43fb5
snap_2019-11-15-19-00.tar.gz Wasabi S3 549.44 MiB fd26c1f05d7334ca281467579c069a35
snap_2019-11-15-18-00.tar.gz Wasabi S3 549.42 MiB 74b77e3e20f7607307b239bba7f62c55
snap_2019-11-15-17-00.tar.gz Wasabi S3 549.34 MiB 6d303743be94ec785dac9125d0fa3c1f
snap_2019-11-15-16-00.tar.gz Wasabi S3 549.02 MiB 6c7afd43727d0bdbcca1eac965c7eb44
snap_2019-11-15-15-00.tar.gz Wasabi S3 548.92 MiB 5adbcd83d1363ef8ce6195a82352eaeb
snap_2019-11-15-14-00.tar.gz Wasabi S3 548.75 MiB 7e3a535bc31b04cbc71e6383224d23f2
snap_2019-11-15-13-00.tar.gz Wasabi S3 548.65 MiB 4ab1c4bd0a851b316721c79e2f938463
snap_2019-11-15-12-00.tar.gz Wasabi S3 548.55 MiB e50ba82b4bb26a5c8f71ac6e40fd0691
snap_2019-11-15-11-00.tar.gz Wasabi S3 548.49 MiB 38bbdb407c510abcb323bbc5c028ed90
snap_2019-11-15-10-00.tar.gz Wasabi S3 548.39 MiB 19d33392eb7d436951fc39ad724c5112
snap_2019-11-15-09-00.tar.gz Wasabi S3 548.36 MiB 35939c033dcc8a1c18346e2f7448504f
snap_2019-11-15-08-00.tar.gz Wasabi S3 548.25 MiB 3d56ab538b1920f1afd0b22edeb8b16a
snap_2019-11-15-07-00.tar.gz Wasabi S3 548.18 MiB 47034879afee3c30b6bcd55a79d63ca5
snap_2019-11-15-06-00.tar.gz Wasabi S3 548.08 MiB 28d77c66bba7cfd4abe3787ed2f22251
snap_2019-11-15-05-00.tar.gz Wasabi S3 548 MiB e5c82e8e98d8bae710cb70d9b005c7d1
snap_2019-11-15-04-00.tar.gz Wasabi S3 548.61 MiB 9d6b4d37ea4f64d30d51341bf25787fd
snap_2019-11-15-03-00.tar.gz Wasabi S3 549.46 MiB deb58134c2f818ec00741f1cbb0b103d
snap_2019-11-15-02-00.tar.gz Wasabi S3 549.37 MiB 0fb6b3f0d9ae280520010763c9d97e01
snap_2019-11-15-01-00.tar.gz Wasabi S3 549.43 MiB 5400a4fd8836b02081f0d65d718f14ae
snap_2019-11-15-00-00.tar.gz Wasabi S3 549.59 MiB 74b7d49d0c4f16585da00bd50bad42cc

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