🤔 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-09-16-06-00.tar.gz Wasabi S3 507.25 MiB 638b22dad45c7b64dbc9de6cb022ea3c
snap_2019-09-16-05-00.tar.gz Wasabi S3 507.23 MiB bf5a2e40784d201dd75771c0f293f764
snap_2019-09-16-04-00.tar.gz Wasabi S3 507.22 MiB 2ef812cc45356512d9cfbbd52c44bf7f
snap_2019-09-16-03-00.tar.gz Wasabi S3 507.25 MiB 698af0dee970c67306464e5ee74e0d60
snap_2019-09-16-02-00.tar.gz Wasabi S3 507.13 MiB 06527ee5dd83a23ab18be1b12c2903aa
snap_2019-09-16-01-00.tar.gz Wasabi S3 507.04 MiB 04d2862b6705821a387e56d0845fe3f2
snap_2019-09-16-00-00.tar.gz Wasabi S3 506.93 MiB c6c9d62cdad5ddfca9e1e618fe21befb
snap_2019-09-15-23-00.tar.gz Wasabi S3 506.98 MiB 8f630d3a9b585f120d42061c231609a9
snap_2019-09-15-22-00.tar.gz Wasabi S3 507.1 MiB adbaac32da5e2c0fd28c491396c9f35a
snap_2019-09-15-21-00.tar.gz Wasabi S3 507.1 MiB e696a5a9d4a517c22ad9aa2a4e6fe89b
snap_2019-09-15-20-00.tar.gz Wasabi S3 506.97 MiB 2708630298c0cda20827affe0a606ebb
snap_2019-09-15-19-00.tar.gz Wasabi S3 507.06 MiB 17896f3fe39c179080131a148fc513e3
snap_2019-09-15-18-00.tar.gz Wasabi S3 507.13 MiB 643a6de01b8f31bf1d609897463e946f
snap_2019-09-15-17-00.tar.gz Wasabi S3 507.07 MiB 7789d9fc2496d4082c80c60205150928
snap_2019-09-15-16-00.tar.gz Wasabi S3 507.53 MiB d268de158272dd7e44120ea449f92d48
snap_2019-09-15-15-00.tar.gz Wasabi S3 507.52 MiB d35db5a0d1d7f0bbc5fef611da377bab
snap_2019-09-15-14-00.tar.gz Wasabi S3 507.54 MiB 8cc4898d8540e5a63b25cb11c9bc8a60
snap_2019-09-15-13-00.tar.gz Wasabi S3 507.32 MiB 5fe6e93833977e1e54fcc6dcd1ab2565
snap_2019-09-15-12-00.tar.gz Wasabi S3 507.15 MiB 57132e5052cc6a145e4baccc9234eb6c
snap_2019-09-15-11-00.tar.gz Wasabi S3 506.79 MiB ecec69fc64eff212e05962bf838769b8
snap_2019-09-15-10-00.tar.gz Wasabi S3 506.54 MiB 38f9e361186122d0feda023e60a4a206
snap_2019-09-15-09-00.tar.gz Wasabi S3 506.29 MiB ddff97ec832763de346b36ba67c2bfcf
snap_2019-09-15-07-00.tar.gz Wasabi S3 505.78 MiB ea45d87d3b65336a73f2bf29b0ccaeb9
snap_2019-09-15-06-00.tar.gz Wasabi S3 505.58 MiB 5f91474c988c7ece885a04bdbf9bdb98
snap_2019-09-15-05-00.tar.gz Wasabi S3 505.44 MiB a9cbc75ea6c9f8d4c355acaa3e17c344
snap_2019-09-15-04-00.tar.gz Wasabi S3 505.79 MiB c8df1cd3e5c1e8d7c13c9ef7f62b3f12
snap_2019-09-15-03-00.tar.gz Wasabi S3 505.56 MiB 052926f912d17729b75607fd7c01d9f7
snap_2019-09-15-02-00.tar.gz Wasabi S3 505.52 MiB 95c0bd6b2979816a1176203ac4e5d450
snap_2019-09-15-01-00.tar.gz Wasabi S3 505.29 MiB e3f6032fb445ed5f63e8d00a90962044
snap_2019-09-15-00-00.tar.gz Wasabi S3 505.01 MiB e4229899c4d686bc09658d2a24f7b171

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