Chain snapshot

A recent copy of the BlockDAG chain database, so you can bring a node up in minutes instead of syncing from genesis.

blockdag-mainnet-latest.tar.zst

32.2 GB compressed · chain 1404

Download snapshot All files

EVM height

—

Captured

—

Compressed

32.2 GB

Chain ID

1404

Node release

rc.65.6

Read this before you restore. This snapshot follows the chain branch served by rpc.welshdag.trade. Some other BlockDAG explorers index a different branch — the two diverged at EVM block 316,002 in February 2026.

If you restore this and then compare balances or transactions against one of those explorers, they will not match. That is expected, not corruption. Use this snapshot if you want a node on the same branch as this pool.

No keys are included. Wallet keystore, node identity and RPC certificates are all stripped. Your node generates its own on first start. Peer history is excluded too.

How to restore

Stop your node completely and let it shut down cleanly.
Move your existing data aside — rename it, do not delete it, until the new one is proven.
Extract the snapshot into your node data directory.
Fix ownership so the node process can write to it.
Start the node and watch it replay forward to the current tip.

# verify the download first
sha256sum -c SHA256SUMS

# move the old data aside, then extract
mv  /srv/blockdag/stack/node-data  /srv/blockdag/stack/node-data.old
mkdir -p /srv/blockdag/stack/node-data
zstd -dc blockdag-mainnet-latest.tar.zst | tar -xf - -C /srv/blockdag/stack/node-data

# the node runs as uid/gid 999 in the standard container
chown -R 999:999 /srv/blockdag/stack/node-data

Expect the first start to take a while — the node rebuilds indexes and replays from the snapshot height to the live tip. That is normal and it is not stuck.

Verify what you downloaded

SHA-256 of the current snapshot:

f61156e003d0448d8439c85552a76b15bb6de4296a8adfd482ce294185bae76c

The shared folder also carries SHA256SUMS and a manifest.json recording the exact height and capture time.