Titan Snapshots
Daily, checksummed Robinhood Chain (chain ID 4663) archive node snapshots. Download a compressed copy of the chain data and get a new node running in minutes instead of syncing from genesis.
Key features
Lightweight & fast
Zstandard compression shrinks the ~68GB live data directory to about 39GB.
Verified & secure
Every archive gets a SHA256 checksum, plus a directory breakdown so you know what's inside before extracting.
Always up to date
Rebuilt daily at 03:00 UTC directly from the live archive node — never more than 24h behind.
Built for node operators
Node secrets, keys, and keystores are excluded — bring your own and extract straight into place.
Available Snapshots
Daily updates| File | Size | Generated | Action |
|---|---|---|---|
| robinhood-snapshot-1784343600.tar.zstLatest | 76.9 GB | ||
| robinhood-snapshot-1784327580.tar.zst | 75.6 GB | ||
| robinhood-snapshot-1783952760.tar.zst | 39.4 GB |
What is Titan Snapshot
Titan Snapshots is a daily snapshot service for the Robinhood Chain archive node. It exists so node operators, indexers, explorers, and RPC providers can bootstrap a new Robinhood Chain node without re-executing the chain's entire history.
- Runs against a live, production Robinhood Chain (chain ID 4663) archive node
- Captures a full copy of that node's data directory once per day
- Compresses the archive with Zstandard and generates a SHA256 checksum
- Publishes the result here for direct download, with no account or API key required
What is a Robinhood Chain Snapshot
A Robinhood Chain snapshot is a point-in-time copy of an archive node's on-disk state: block headers, transaction history, and account/contract state up to the block height at capture time.
- Format: a single
.tar.zstarchive containing adata/directory - Content: everything a Nitro node stores under its
.arbitrumhome directory - Excludes:
jwtsecret, keystores, and anything matching*secret*/*private* - Does not include: your node's own configuration, genesis file, or L1 credentials — you supply those separately
Archive Node vs Full Node
This snapshot is captured from an archive node, not a pruned full node. The distinction matters if you're choosing which kind of node to run:
| Property | Full node | Archive node |
|---|---|---|
| Historical state | Pruned after recent blocks | Retained in full |
| Disk usage | Lower | Higher (~68GB+ live) |
| Typical use case | Wallets, submitting transactions, recent reads | Indexers, explorers, RPC providers, full-history eth_getLogs |
| This snapshot | — | ✓ captured from an archive node |
How Snapshots Work
- Captured directly from a live Robinhood Chain archive node's data directory
- Compressed with Zstandard, shrinking ~68GB down to roughly 38–40GB
- Rebuilt daily at 03:00 UTC — see the Status page for the exact schedule
- Checksummed with SHA256 for integrity verification — see the Verify page
- The last 3 daily snapshots are retained; older ones are pruned automatically
- Restoring one is a two-step process: download + verify, then extract — see the Documentation page
Frequently Asked Questions
What is a Robinhood Chain snapshot?
A Robinhood Chain snapshot is a compressed copy of an archive node's data directory for chain ID 4663 (the Arbitrum Orbit / Nitro-based Robinhood Chain). Extracting one into a fresh node lets it start from the snapshot's block height instead of syncing from genesis.
How do I sync Robinhood Chain faster?
Download the latest snapshot below, verify its SHA256 checksum, and extract it into your node's data directory before starting it. This replaces re-executing the chain's full history with a single archive download — see the Documentation page for the exact steps.
Where can I download Robinhood Chain snapshots?
The latest snapshot and the previous daily snapshots are listed on the homepage with direct download links. All retained snapshots are also browsable at /snapshots.
How do I verify a snapshot?
Every snapshot ships with a SHA256 checksum sidecar file. Download both the archive and its .sha256 file, then run sha256sum -c against it — see the Verify page for a copy-pasteable command.
How do I restore an archive node from a snapshot?
Extract the downloaded .tar.zst into your node's data directory with tar -I zstd -xf <file> -C <path>, then start the node as usual — it resumes from the snapshot's block height. Full steps are on the Documentation page.
How often are snapshots generated?
Daily, at 03:00 UTC, captured directly from a live Robinhood Chain archive node. The current schedule and next run time are on the Status page.
How large are Robinhood Chain snapshots?
Roughly 38–40GB compressed, down from a live archive data directory of about 68GB, using Zstandard compression. The exact current size is shown in the Snapshot Details on the homepage.
Which node version is supported?
Snapshots are captured from a node running offchainlabs/nitro-node:v3.11.2-3599aca in archive mode. See the Documentation page for the full docker-compose setup.