Sei Mainnet pacific-1 Height— Snapshot— connecting

Snapshot files

What you download, what is inside it, and what it is tied to. All of it read from the live manifest.

Height

—

On the wire

—

zstd -3, hashes stripped

Parts

—

fetched in parallel

State age

—

Build time

—

State engine

memIAVL

ss-enable must be false

—

/manifests/mainnet/latest.jsonlatest.json ↗

Putting it on a node

The script fills an empty node home. For the requirements and what to expect, see Install a node.

One line

curl -fsSL https://dev-labs.seistream.app/install.sh | bash

refuses a non-empty data/state_commit
refuses a seid that is not the version the state was written with
checks every part's sha256 while it streams, stops on a mismatch
recomputes the stripped hashes and checks every tree root against the snapshot's commit info
never touches priv_validator_key.json or node_key.json

read the file ↗

What it does, step by step

M=$(curl -s $B/manifests/mainnet/latest.json)

# 1. every part, in parallel
range part → zstd -dc → write at
             path + offset
tar part   → zstd -dc | tar -x

# 2. hashes back, per memIAVL tree
hashtool refill nodes leaves kvs
hashtool roots  → must equal __metadata

# 3. two keys in app.toml
ss-enable = false
[state-sync] snapshot-interval = 0

The parts

A part's filename is its sha256. Large files are split into byte ranges that land straight in place; small files travel in tar parts.

#	sha256, which is also the filename	Unpacks to	Size
…

—all parts or none

Fingerprints

app_hash

—

sha256 of parts

—

The sha256 of the parts' own sha256s, sorted and concatenated — one fingerprint for the whole snapshot. The first number is the chain's; this one is ours.

What is inside, and what is not

Ships in the archive

memIAVL snapshot —: kvs, nodes, leaves — the last two without their SHA-256 hashes
memIAVL changelog after the snapshot, replayed by the node on start
state.db + blockstore.db: the kilobytes a light-client bootstrap writes for this height — not block history
wasm/state: CosmWasm contract code

Deliberately absent

state store (SS) — historical queries; a node does not need it to follow the chain
wasm cache — rebuilt on demand
block history — your node fetches blocks from peers
priv_validator_state.json, cs.wal, evidence.db, tx index

What this snapshot is tied to

seid

—

Chain

pacific-1

Sei mainnet

memIAVL record

48 B

16 shipped + 32 recomputed

Read out of the binary that wrote the state, not from a go.mod. Run exactly this version: a different seid once rewrote the changelog of a state it could not verify.

How long we keep it

Parts kept

—

current and recent snapshots

Disk they occupy

—

on the builder

Grace

—

after a newer publish

—

/manifests/mainnet/status.jsonstatus.json ↗