Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 14 additions & 2 deletions skill/references/ecosystem/node-operations.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,13 +47,13 @@ seid init <YOUR_MONIKER> --chain-id pacific-1
# seid init <YOUR_MONIKER> --chain-id pacific-1 --mode validator
```

> **Never start from genesis on a live network** — it panics with `integer divide by zero`. Bootstrap via state sync (below) or a snapshot.
> **Never start from genesis on a live network** — it panics with `integer divide by zero`. Bootstrap via state sync (below). A provider snapshot is a fallback that requires trusting the provider — see Provider Snapshots below.

---

## State Sync (Recommended for Fast Bootstrap)

State sync fetches a recent snapshot instead of replaying all history — reduces sync from days to minutes.
State sync fetches a recent snapshot instead of replaying all history — reduces sync from days to minutes. It is the only officially supported bootstrap method for Sei Mainnet.

### Automated State Sync

Expand Down Expand Up @@ -96,6 +96,18 @@ State sync peers:

---

## Provider Snapshots (Trust Required)

A provider snapshot is a third-party archive of another node's `data/` and `wasm/` directories, extracted into `$HOME/.sei`.

- Restoring one **requires trusting the provider**. A malicious or compromised provider can corrupt a snapshot in ways that are not immediately detectable.
- The node **cannot verify the historical State Store (SS) data** in a snapshot at all.
- State sync, by contrast, verifies the restored state against the app hash in a block header that the light client has verified.

Recommend state sync. Suggest a provider snapshot only when state sync cannot do the job — for example, an archive node, which needs history that state sync does not restore — and always say that it requires trusting the provider. For an archive node, the snapshot itself must be an archive (unpruned) snapshot: a snapshot keeps the source node's pruning, so restoring a pruned one and then turning pruning off cannot bring back the missing history. For the restore procedure, link https://docs.sei.io/node/snapshot.

---

## Directory Structure

```
Expand Down
2 changes: 1 addition & 1 deletion skill/references/resources.md
Original file line number Diff line number Diff line change
Expand Up @@ -123,7 +123,7 @@ Additional RPC providers: https://docs.sei.io/learn/rpc-providers

| Resource | URL |
|---|---|
| Polkachu snapshots | https://polkachu.com/tendermint_snapshots/sei |
| Polkachu snapshots (⚠️ third-party — restoring one requires trusting the provider; prefer state sync) | https://polkachu.com/tendermint_snapshots/sei |
| NodeJumper | https://nodejumper.io/sei |
| State sync (testnet) | https://rpc-testnet.sei-apis.com |

Expand Down
Loading