The full memIAVL state ships without its SHA-256 hashes. Your machine recomputes them in minutes and checks every tree root against the snapshot's own commit info before the node starts. One command.
Run it on the machine that will host the node. It refuses to touch a non-empty data/state_commit and never writes priv_validator_key.json or node_key.json.
nodes/leaves are rebuilt, and every tree root is compared with the snapshot's commit info. On any mismatch it stops and tells you not to start the node.ss-enable = false and [state-sync] snapshot-interval = 0 in app.toml, persistent peers in config.toml. Then: seid start.The node replays the shipped changelog up to the snapshot height (thousands of blocks per second), then catches up from peers.
| Part | Unpacks to | Raw | Download |
|---|---|---|---|
| … | |||
Why it is small. Sei keeps its state in memIAVL: an IAVL tree laid out flat on disk as kvs, nodes and leaves. Every node and leaf record is 48 bytes, and 32 of them are a SHA-256 hash — random bytes that no compressor touches. They are a third of the state and pure function of the rest, so we cut them out (48 → 16 bytes per record) and your machine computes them again. The historical state store is not shipped at all; a fresh node does not need it to follow the chain.
Why you can trust it. Hashes are recomputed on your machine, not copied from ours, and every tree root must equal the store hash recorded in the snapshot's __metadata. The published height's app_hash is checked against a quorum of independent public RPCs before anything is published, and every part is verified by sha256 as it downloads.
How it is made. Once an hour the node is stopped, the immutable memIAVL snapshot is hard-linked (no bytes copied), the changelog after it and the Tendermint databases are copied, and the node starts again. The copy is stripped, split into parts and compressed while the node runs on. Parts are named by their sha256, so a part that did not change is not stored twice.
What we cannot promise. The snapshot is as old as the last capture plus its build — about an hour at best. Network upgrades need the matching seid; the manifest always names the version the data was written with.