🤔 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-04-25-17-00.tar.gz Wasabi S3 416.45 MiB 38a696e76339a52a548a5e4283b69268
snap_2019-04-25-16-00.tar.gz Wasabi S3 416.09 MiB d0a4ac408fea62b4f774d68a9623fb2e
snap_2019-04-25-15-00.tar.gz Wasabi S3 415.93 MiB b7015f75225632ac8c548790e0c96371
snap_2019-04-25-14-00.tar.gz Wasabi S3 415.57 MiB 3fe7069f1ecf48ccdeae5bb02aefb766
snap_2019-04-25-13-00.tar.gz Wasabi S3 415.27 MiB f3ad6c3bab9d7a7bededb999bc95e1ca
snap_2019-04-25-12-00.tar.gz Wasabi S3 415.05 MiB f14bc485a52d086ab76b16f5f8aaf440
snap_2019-04-25-11-00.tar.gz Wasabi S3 414.9 MiB 184b6aeb976e6696de3ae7120f0d1b27
snap_2019-04-25-10-00.tar.gz Wasabi S3 414.61 MiB 92e59ab6b81c287a0b6b1b46e724b589
snap_2019-04-25-09-00.tar.gz Wasabi S3 414.57 MiB 7ad8a9201b25fffafb68a20a45df6c85
snap_2019-04-25-08-00.tar.gz Wasabi S3 414.2 MiB 2c55891dfd423c8aacb956b518824680
snap_2019-04-25-07-00.tar.gz Wasabi S3 413.94 MiB c6bc879cde95b7b8b6c1afd3074b7c77
snap_2019-04-25-06-00.tar.gz Wasabi S3 413.55 MiB 61cf438251ebabf2d807315e4c432e27
snap_2019-04-25-05-00.tar.gz Wasabi S3 413.49 MiB b64bd228e505421d9fb30f56a655d000
snap_2019-04-25-04-00.tar.gz Wasabi S3 413.51 MiB 63fd7cc333f25f938ee8f6665970ac22
snap_2019-04-25-03-00.tar.gz Wasabi S3 413.34 MiB 16fe2d0aa5806bd4d67d79ea7dcdaffd
snap_2019-04-25-02-00.tar.gz Wasabi S3 413.25 MiB 0764bbb22a565fc194bdf0cd34b131c7
snap_2019-04-25-01-00.tar.gz Wasabi S3 413.25 MiB 3f65cadf9a92dc525e569ade4c86cbd6
snap_2019-04-25-00-00.tar.gz Wasabi S3 413.27 MiB 4ae14770f82ca83e40b5cd495ac26e0c
snap_2019-04-24-23-00.tar.gz Wasabi S3 413.29 MiB c3b04a5a76013ee0c757d7bbc271accf
snap_2019-04-24-22-00.tar.gz Wasabi S3 413.17 MiB 6cbb7c16d7d49a1a4995d33743364dc2
snap_2019-04-24-21-00.tar.gz Wasabi S3 413.11 MiB 4e7959a0eb8dff38218b3afd999c4471
snap_2019-04-24-20-00.tar.gz Wasabi S3 413.15 MiB 3d55843fb50adb6ad8460ebcde591de5
snap_2019-04-24-19-00.tar.gz Wasabi S3 413.19 MiB 952b8d0648967409053544678ffa1714
snap_2019-04-24-18-00.tar.gz Wasabi S3 413.2 MiB e759e9abc006abd25d666e4e0c716461
snap_2019-04-24-17-00.tar.gz Wasabi S3 412.99 MiB 80920807b43f823ffec55fc71feab2f2
snap_2019-04-24-16-00.tar.gz Wasabi S3 412.7 MiB a61626733f2fb9fcb5db14852289404d
snap_2019-04-24-15-00.tar.gz Wasabi S3 412.75 MiB 69c11c367c9e30111379230fad718bf2
snap_2019-04-24-14-00.tar.gz Wasabi S3 412.64 MiB 668ea8563112274801f54bd8e1bcb572
snap_2019-04-24-13-00.tar.gz Wasabi S3 412.5 MiB f193c21208f42838d25b5b7ad4e32316
snap_2019-04-24-12-00.tar.gz Wasabi S3 412.35 MiB c7408abe27cc2d26782a295b1e811ed8
snap_2019-04-24-11-00.tar.gz Wasabi S3 411.92 MiB da767dc71476270faf4f8beefb057c18
snap_2019-04-24-10-00.tar.gz Wasabi S3 410.88 MiB 303abdf7cb4f3c194e504d0f9d249971
snap_2019-04-24-09-00.tar.gz Wasabi S3 409.23 MiB f5f04718ff9f25e2f0193f5500c50e8a
snap_2019-04-24-08-00.tar.gz Wasabi S3 409.12 MiB 553019912526cef9a5e105b57e042689
snap_2019-04-24-07-00.tar.gz Wasabi S3 408.72 MiB 8af7b421189ed8615ee9dc6a27552e98
snap_2019-04-24-06-00.tar.gz Wasabi S3 408.46 MiB 0b3f4641fef12f4b3a7d9499c79bbb30
snap_2019-04-24-05-00.tar.gz Wasabi S3 408.34 MiB bdf276e4fce35b6fe6b42d5c59884abc
snap_2019-04-24-04-00.tar.gz Wasabi S3 408.14 MiB 790e6740f6e578f0b17f000e1c59d63a
snap_2019-04-24-03-00.tar.gz Wasabi S3 407.82 MiB 4f06b49b526c281b618d48cb2e7cf438
snap_2019-04-24-02-00.tar.gz Wasabi S3 407.73 MiB 2dee8eb344103edb218d50aba09a2738
snap_2019-04-24-01-00.tar.gz Wasabi S3 409.71 MiB 0298eb65768a0db15a756506b0e793d1
snap_2019-04-24-00-00.tar.gz Wasabi S3 409.81 MiB 8e703402815300479d2ff81e95a745a0

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