Install a node

With options:

--home DIR	node home, default ~/.sei. Without a config inside it, the script runs seid init and fetches the genesis.
--jobs N	parallel downloads, default 8. On a 1 Gbit/s line 8–16 saturate it.
--seid PATH	which binary to check the version of, default seid in PATH.
--force-version	install even if your seid is a different version. Do not, unless you know why.

1. Checks. Linux x86_64, curl, zstd, tar, python3, sha256sum; your seid version against the manifest; free disk; an empty data/state_commit.
2. Download. All parts at once. Each part's sha256 is checked while it streams; byte ranges are written straight to their place, small files unpack from tar — no archive is ever stored.
3. Recompute. The SHA-256 hashes stripped from memIAVL nodes/leaves are rebuilt with hashtool (its sha256 is in the manifest), and every tree root is compared with the snapshot's commit info. Any mismatch stops the script with “do not start the node on this data”.
4. Configure. ss-enable = false and [state-sync] snapshot-interval = 0 in app.toml; persistent peers in config.toml; state sync off.

First minutes. memIAVL replays the changelog shipped with the snapshot up to the published height — on our builder that took about five minutes. Then the node checks its app_hash against the Tendermint state, which was written for exactly that height by a light-client bootstrap, and starts fetching blocks from peers.

Then. It catches up the blocks produced since the snapshot. Our own test node from the same kind of copy was at the head 318 s after start.

Upgrades. The manifest names the seid version the state was written with. After a network upgrade the next snapshot is written by the new binary; run that one.