🤔 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-10-13-20-00.tar.gz Wasabi S3 519.46 MiB 744ea03e9d323bdb09b4b38f46abb950
snap_2019-10-13-19-00.tar.gz Wasabi S3 519.63 MiB 232e32803dd604db9cb6bd1864f60ab9
snap_2019-10-13-18-00.tar.gz Wasabi S3 519.83 MiB 98feee07b06a8b2ce1a420a40c627501
snap_2019-10-13-17-00.tar.gz Wasabi S3 520.01 MiB a9047184f11d5a07e8358b44349dd45e
snap_2019-10-13-16-00.tar.gz Wasabi S3 520.06 MiB 2deb5f3da38f342becb5f51bd90af05b
snap_2019-10-13-15-00.tar.gz Wasabi S3 519.89 MiB 7f222663d99a84928ae0f6d96892c3d2
snap_2019-10-13-14-00.tar.gz Wasabi S3 520.03 MiB 0db4b152d4a51331b0b40a3f4dbfbbe2
snap_2019-10-13-13-00.tar.gz Wasabi S3 519.85 MiB 7c5980fec2c86c7fd2988566fb9c5ef0
snap_2019-10-13-12-00.tar.gz Wasabi S3 519.89 MiB 618bb7b424cb784124b4cc9f4e30c903
snap_2019-10-13-11-00.tar.gz Wasabi S3 519.94 MiB beff45b75ad4094f3919c589f66cacf6
snap_2019-10-13-10-00.tar.gz Wasabi S3 520 MiB f094ae41201bd8e31ebcc6364e58c6b8
snap_2019-10-13-09-00.tar.gz Wasabi S3 519.99 MiB a3460385052ff0cfde3b9b5afb667fcc
snap_2019-10-13-08-00.tar.gz Wasabi S3 520.13 MiB 3bdb0548b3e654bfc5020fc29dfa39ab
snap_2019-10-13-07-00.tar.gz Wasabi S3 520.1 MiB 101670763be0d4648dc69f845535af7f
snap_2019-10-13-06-00.tar.gz Wasabi S3 520.06 MiB f4559262fbcb6afdb0cdcd697d3e3317
snap_2019-10-13-05-00.tar.gz Wasabi S3 519.64 MiB 81ab586826a3b21b5eabcd9f31cb4992
snap_2019-10-13-04-00.tar.gz Wasabi S3 519.44 MiB d0c28d20fca1a4e66082572863631606
snap_2019-10-13-03-00.tar.gz Wasabi S3 523.97 MiB 8eb5190bff16bdb6d5e346f9ec2c19d4
snap_2019-10-13-02-00.tar.gz Wasabi S3 523.77 MiB 53873c3ad1c4acc1fd33fb8690717e1c
snap_2019-10-13-01-00.tar.gz Wasabi S3 523.46 MiB c9d4f059b8865e19a7b23bf8bf1ea2a6
snap_2019-10-13-00-00.tar.gz Wasabi S3 523.26 MiB f0ceea256906204497e3e79503779c99
snap_2019-10-12-23-00.tar.gz Wasabi S3 523.34 MiB 719b671e1372231f15c5c48cc1b53d3c
snap_2019-10-12-22-00.tar.gz Wasabi S3 523.48 MiB 35a43672c19196b0b024f6cacfa17b64
snap_2019-10-12-21-00.tar.gz Wasabi S3 523.48 MiB 3efc1c4204210e7eb751953257e528b0
snap_2019-10-12-20-00.tar.gz Wasabi S3 523.42 MiB 2d6e6e573a31a83b1a9ea919019e2538
snap_2019-10-12-19-00.tar.gz Wasabi S3 523.47 MiB cdb85dfe3402bb5869c3bea6e380e0c3
snap_2019-10-12-18-00.tar.gz Wasabi S3 523.81 MiB 5c5b34a8633bc6d260adb4531e38f344
snap_2019-10-12-17-00.tar.gz Wasabi S3 523.53 MiB 1a70d53cbbcce63d1e16b73b618c0e7e
snap_2019-10-12-16-00.tar.gz Wasabi S3 523.11 MiB 026ba469ebb114761f1b0377f94fd0d5
snap_2019-10-12-15-00.tar.gz Wasabi S3 522.88 MiB 256db547141e4d3ba442d20d30e45066
snap_2019-10-12-14-00.tar.gz Wasabi S3 522.66 MiB d234c31e52f53b8ac3ebec2aa0514a30
snap_2019-10-12-13-00.tar.gz Wasabi S3 522.11 MiB 421380538ef8550cb8302771900229d9
snap_2019-10-12-12-00.tar.gz Wasabi S3 521.84 MiB ef9ad62389ecd18fa01bc90e80a7ac11
snap_2019-10-12-11-00.tar.gz Wasabi S3 522.45 MiB e6d418a18d8790053c0dc589c9beab2a
snap_2019-10-12-10-00.tar.gz Wasabi S3 522.43 MiB 1ccd802652e9260451951c38a4c5ca0e
snap_2019-10-12-09-00.tar.gz Wasabi S3 523.37 MiB b18be871b2b893738f45e527758aa7c8
snap_2019-10-12-08-00.tar.gz Wasabi S3 522.98 MiB 4598f1d7af2ec1ab0c3527cd25087aca
snap_2019-10-12-07-00.tar.gz Wasabi S3 522.9 MiB 945a8ad9d9c86c6359bcc76998d7187a
snap_2019-10-12-06-00.tar.gz Wasabi S3 522.79 MiB 02ec3fb34e8cc0b35f9364f33a79b80d
snap_2019-10-12-05-00.tar.gz Wasabi S3 523.08 MiB 257fc6a1bf8feff4494164c30845228a
snap_2019-10-12-04-00.tar.gz Wasabi S3 522.81 MiB dc99855791ab821bcce9c99c29939d6e
snap_2019-10-12-03-00.tar.gz Wasabi S3 522.49 MiB c0bbd80e5e95dc867c72c5877974e17e
snap_2019-10-12-02-00.tar.gz Wasabi S3 522.58 MiB ca53b4b37d837140ccaf8003d5e7d80b
snap_2019-10-12-01-00.tar.gz Wasabi S3 522.44 MiB 4b96e9f8c14777e0910d9435d6ce40f0
snap_2019-10-12-00-00.tar.gz Wasabi S3 522.69 MiB baf94616bec0ac6d29282d81e235afce

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