Skip to content

πŸ“¦ Using Jovay Ledger Snapshots ​

πŸ“– Introduction ​

Jovay publishes State Derivation (SD) Sequencer ledger snapshots on a regular schedule so you can bootstrap an SD Sequencer from recent rollup state without syncing the full chain history.

πŸ“Œ Scope: These snapshots are for SD Sequencers only. They are not compatible with standard RPC node deployment; use the separate RPC node artifacts and instructions for that purpose.

Each release ships three artifacts for a given network:

ArtifactDescription
πŸ“œ genesis.confFixed genesis configuration for the network (same file for every release on that network).
πŸ—œοΈ <YYYYMMDD>_<BLOCK_HEIGHT>.tar.gzCompressed ledger database snapshot.
βš“ snapshot_anchor.jsonL1 cursor seed for State Derivation. The current implementation begins scanning from the following L1 block.

Archive names follow YYYYMMDD_BLOCKHEIGHT.tar.gz (YYYYMMDD = publish date, BLOCK_HEIGHT = L2 stable height in the snapshot). The matching anchor is published at state-derivation/YYYYMMDD_BLOCKHEIGHT/snapshot_anchor.json.

πŸ“Œ Retention: Use the newest published artifacts listed for your network below. Older archives may be removed after a replacement is published; do not rely on their continued availability.

⏱️ Cadence: Snapshots are published approximately every 14 days.

⚠️ Blob availability: An SD Sequencer must fetch every rollup Blob published after the snapshot's L1 anchor. Ethereum consensus nodes are required to serve Blob sidecars for only 4,096 epochs (about 18 days). Always use the latest snapshot below; an older snapshot may no longer be usable with a standard Beacon provider even if its archive is still downloadable.

πŸ’Ύ Capacity planning: The current Testnet archive is 137,185,269,406 bytes (about 127.8 GiB compressed). A previous Testnet ledger occupied approximately 360 GiB uncompressed; allow for further growth. Keep the archive and extracted ledger on the same filesystem only if it has at least 600 GiB free, including room for database growth. Snapshot sizes will increase as the chain grows.

πŸ’Ύ Mainnet capacity: The current Mainnet archive is 20,827,535,188 bytes (about 19.4 GiB compressed). Budget for the downloaded archive and restored databases, plus room for database growth and recovery.

🎯 What You Need From a Snapshot ​

Before starting an SD Sequencer, download all three artifacts for your target network from the table below:

  1. βœ… genesis.conf
  2. βœ… Latest <YYYYMMDD>_<BLOCK_HEIGHT>.tar.gz
  3. βœ… Matching snapshot_anchor.json

βœ… Testnet image: Product version 0.15.0, published as jovay-release-registry.cn-hongkong.cr.aliyuncs.com/jovay/l2-sequencer:0.15.0-rc1, has been validated end to end on Testnet. This does not establish compatibility with every later snapshot; see the network-specific availability and validation notes below.

πŸ“Š Latest Jovay Ledger Snapshots ​

Testnet (Sepolia L1) ​

The latest Testnet snapshot was published on 2026-10-23. Its L2 stable height is 47889111 and its matching L1 anchor is 11975757. Before starting SD, confirm that your Beacon provider can still serve all required Blob data after this anchor; publication does not guarantee ongoing Blob availability.

FileRecommended Sequencer versionL2 block heightFile nameChecksumsDownload
πŸ“œ genesis.conf0.15.0-rc1β€”genesis.confMD5: 1b6ad3d9fa67a596ca094e89bd2280ee
SHA-256: 772cdd59b915787a5bca57f7bba0584333081f8749a7f702f5bba60819000fad
link
πŸ—œοΈ Ledger snapshot0.15.0-rc14788911120261023_47889111.tar.gzMD5: 8373cd61d0104767c7a7bcfc1ab81c1e
SHA-256: fdc5e044adec86ec22b894ae0d5f1db46dd59bd7ad78d6ccc41633486ad9541a
link
βš“ snapshot_anchor.json0.15.0-rc147889111snapshot_anchor.jsonMD5: e18ecb3c4b7cce99bc00d61872eb0735
SHA-256: 6cdfa84a06eab19ca17c2ea54c47c7a8f5a67298b704c7fbc26a3fea5cfab7e0
link

πŸ“Œ Validation status: Snapshot creation, upload, and public HTTPS checks succeeded. The archive checksums above are the publisher's release values; verify your complete download before use. This specific snapshot has not yet been revalidated end to end by restoring an SD Sequencer and deriving subsequent batches with the public 0.15.0-rc1 image.

Mainnet (Ethereum L1) ​

The latest Mainnet snapshot was published on 2026-11-19. Its L2 stable height is 14474115 and its matching L1 anchor is 26447170.

FileL2 block heightFile nameChecksumsDownload
πŸ“œ genesis.confβ€”genesis.confMD5: 502c910cbc21137c606621622fe67d28
SHA-256: d436f01b2e25d1946e63d885cb1dd3136da0e3d3beaf300f6f3f4482aff6b5d9
link
πŸ—œοΈ Ledger snapshot1447411520261119_14474115.tar.gzMD5: 50ea28c847cfbda3914b02e7f921fcfd
SHA-256: 2f0f44e688fb7f6f35f8fc5fdb3801f2ef2787b4dd988e6d612be95fdfcec1a4
link
βš“ snapshot_anchor.json14474115snapshot_anchor.jsonMD5: 218e70067c425d39c2c615160b3bbccc
SHA-256: 03f129b53ad677e1c91fdd75bd8600eabd1db09632325a918d65f0c87065f19a
link

πŸ“Œ Validation status. Both files are available over HTTPS. The archive size matches the upload record, and the downloaded anchor matches its published checksums. Verify your complete downloads against the release checksums above. End-to-end validation of snapshot restore and batch derivation with the public 0.15.0-rc1 image is pending for this release.

After downloading all three artifacts, verify each file's SHA-256 checksum against the table above. MD5 values are retained for compatibility and accidental-transfer checks, but SHA-256 is the primary integrity check:

bash
sha256sum genesis.conf
sha256sum <YYYYMMDD>_<BLOCK_HEIGHT>.tar.gz
sha256sum snapshot_anchor.json

# Optional compatibility check
md5sum genesis.conf <YYYYMMDD>_<BLOCK_HEIGHT>.tar.gz snapshot_anchor.json

πŸ—‚οΈ Snapshot Archive Structure ​

The archive has one top-level public/ directory. It contains 11 database directories and no loose files at that level:

Example (tree -L 1 public after extraction):

text
public/
β”œβ”€β”€ BlockBodySliceKvDB
β”œβ”€β”€ BlockHeaderKvDB
β”œβ”€β”€ BlockIndexKvDB
β”œβ”€β”€ BlockMetaKvDB
β”œβ”€β”€ BlockRwSetDB
β”œβ”€β”€ ContractCodeKvDB
β”œβ”€β”€ MetaKvDB
β”œβ”€β”€ PersistTxKvDB
β”œβ”€β”€ ProofKvDB
β”œβ”€β”€ StateDB
└── TxIndexKvDB

11 directories, 0 files

When deploying an SD Sequencer, extract these folders into data/public/ β€” see Start a State Derivation Sequencer.

Snapshots from a multi-disk source use the same layout: the database directories from its data roots are combined under a single public/. You do not need to reproduce the source node's disk mounts. Source-local metadata such as local_storage/, meta_store/, and metasvc_db/ is not included. Initialize the target node first, stop it, and replace only its data/public/, preserving the target's own metadata.

βš“ snapshot_anchor.json Format ​

For example, the Testnet snapshot 20261023_47889111 has the following matching file:

json
{
  "l1_start_block_number": 11975757
}
FieldDescription
l1_start_block_numberInitial value of the persisted L1 indexer cursor. The current implementation scans from l1_start_block_number + 1. Always use the snapshot_anchor.json published with your snapshotβ€”do not guess or edit this value.

πŸš€ Next Steps ​

Ready to run a node? Continue with Start a State Derivation Sequencer.

For Jovay RPC URLs and chain IDs, see Network Information.