From 7c0edf3d4b444ab4bb391ad10a13f3d7939e526d Mon Sep 17 00:00:00 2001 From: alexander-sei Date: Fri, 20 Nov 2026 18:08:49 +0100 Subject: [PATCH 1/2] fix: warn that provider snapshots require trusting the provider node-operations.md offered a provider snapshot as an equal alternative to state sync ("Bootstrap via state sync (below) or a snapshot"), and resources.md listed a snapshot provider with no caveat. Agents repeated that as a plain alternative bootstrap path. Restoring a provider snapshot trusts the provider: a malicious or compromised provider can corrupt it in ways that are not immediately detectable, and the node cannot verify the historical State Store data in it. State sync is the only officially supported bootstrap method for Sei Mainnet. - node-operations.md: point the genesis note at state sync, state that state sync is the supported method, and add a Provider Snapshots (Trust Required) section that tells agents when a snapshot is appropriate and to always state the trust requirement. - resources.md: flag the Polkachu snapshots row, matching the inline style used for the retired Oracle precompile. Co-authored-by: Cursor --- skill/references/ecosystem/node-operations.md | 16 ++++++++++++++-- skill/references/resources.md | 2 +- 2 files changed, 15 insertions(+), 3 deletions(-) diff --git a/skill/references/ecosystem/node-operations.md b/skill/references/ecosystem/node-operations.md index 78cdcce..35b19c6 100644 --- a/skill/references/ecosystem/node-operations.md +++ b/skill/references/ecosystem/node-operations.md @@ -47,13 +47,13 @@ seid init --chain-id pacific-1 # seid init --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 @@ -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 the restore procedure, link https://docs.sei.io/node/snapshot. + +--- + ## Directory Structure ``` diff --git a/skill/references/resources.md b/skill/references/resources.md index 58905d8..4a9c6f3 100644 --- a/skill/references/resources.md +++ b/skill/references/resources.md @@ -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 | From a1d9f413d12cbcd9c44489510a52078b4c3dc0dc Mon Sep 17 00:00:00 2001 From: alexander-sei Date: Fri, 20 Nov 2026 18:21:01 +0100 Subject: [PATCH 2/2] fix: archive nodes need an archive (unpruned) snapshot A provider snapshot keeps the source node's pruning, so restoring a pruned snapshot and then turning pruning off cannot bring back the missing history. Say so in the archive-node example, per review feedback. Co-authored-by: Cursor --- skill/references/ecosystem/node-operations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/skill/references/ecosystem/node-operations.md b/skill/references/ecosystem/node-operations.md index 35b19c6..0eae4ac 100644 --- a/skill/references/ecosystem/node-operations.md +++ b/skill/references/ecosystem/node-operations.md @@ -104,7 +104,7 @@ A provider snapshot is a third-party archive of another node's `data/` and `wasm - 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 the restore procedure, link https://docs.sei.io/node/snapshot. +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. ---