Skip to content

docs(node): warn that snapshots require trusting the provider - #110

Merged
alexander-sei merged 1 commit into
mainfrom
docs/snapshot-trust-warning
Nov 20, 2026
Merged

alexander-sei merged 1 commit into
mainfrom
docs/snapshot-trust-warning

Conversation

@alexander-sei

@alexander-sei alexander-sei commented Nov 20, 2026 •

Copy link
Copy Markdown
Collaborator

What is the purpose of the change?

Correct existing documentation. The snapshot sync guide presented provider snapshots as an equal alternative to state sync and never said that restoring one means trusting the provider. The troubleshooting page went further and called snapshot providers "trusted".

Describe the changes to the documentation

  • node/snapshot.mdx: adds a warning at the top of the page. Restoring a snapshot requires trusting the provider. A malicious or compromised provider could corrupt a snapshot in ways that are not immediately detectable, and the node cannot verify the historical state in a snapshot at all. The warning points readers to state sync, the only officially supported bootstrap method for Sei Mainnet.
  • node/troubleshooting.mdx: the AppHash recovery steps said to download a snapshot "from trusted providers (Polkachu, PublicNode)". Step 3 now says to resync with state sync, or with a snapshot from a provider you trust.

Audience: node operators and validators who bootstrap or resync a node.

Notes

Made with Cursor

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 in it. State sync is the only officially supported bootstrap method for Sei Mainnet.

Add that warning to the top of the snapshot sync guide, and stop the AppHash recovery steps in troubleshooting from calling snapshot providers trusted.

Co-authored-by: Cursor <cursoragent@cursor.com>
@mintlify

mintlify Bot commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
sei-docs 🟢 Ready View Preview Nov 20, 2026, 5:10 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@cursor

cursor Bot commented Nov 20, 2026 •

Copy link
Copy Markdown

PR Summary

Low Risk
Documentation-only changes clarifying bootstrap trust assumptions; no code or operational behavior changes.

Reviewed by Cursor Bugbot for commit 3de79a4. Bugbot is set up for automated code reviews on this repo. Configure here.

@seidroid seidroid Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR adds a warning that restoring a snapshot means trusting the provider. It also stops calling specific snapshot providers "trusted" on the troubleshooting page. The change is small and correct; the notes below are optional improvements.

Findings: 0 blocking | 5 non-blocking | 2 posted inline

Blockers

  • None at the file/PR level.

Non-blocking

  • The Cursor second-opinion review produced no output (cursor-review.md was empty).
  • Codex flagged the PR body's note asking someone to run Sync agent skills from sei-skill after merge as a possible prompt injection. That note is addressed to maintainers as a follow-up, and nothing in the diff acts on it, so I don't consider it an injection. Still, a maintainer should check sei-protocol/sei-skill#23 before running the sync.
  • The new wording says state sync is "the only officially supported bootstrap method for Sei Mainnet". No other page in node/ makes this claim. Confirm it with the node or infrastructure team, and consider repeating it on node/statesync.mdx so the pages stay consistent.
  • 2 suggestion(s)/nit(s) flagged inline on specific lines.

Comment thread node/snapshot.mdx
description: 'Detailed guide for using snapshots to join the network'
keywords: ['sei node', 'blockchain node', 'node configuration', 'seidb', 'node maintenance', 'system operations']
---
<Warning>**Restoring a snapshot requires you to trust the snapshot provider.** A malicious or compromised provider could corrupt a snapshot in ways that are not immediately detectable. Your node cannot verify the historical state in a snapshot at all. For safe bootstrapping, use [state sync](/node/statesync). It is the only officially supported bootstrap method for Sei Mainnet.</Warning>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[suggestion] This sends readers to state sync as the safe option, but state sync also relies on a trust anchor. The trust_height and trust_hash it uses come from the configured RPC endpoint (see node/statesync.mdx around line 76), so a compromised endpoint could supply a false anchor. Consider adding a short clause such as "…use state sync with RPC endpoints you trust" so readers don't assume state sync needs no trust at all. (Raised by Codex; I agree.)

Comment thread node/snapshot.mdx
description: 'Detailed guide for using snapshots to join the network'
keywords: ['sei node', 'blockchain node', 'node configuration', 'seidb', 'node maintenance', 'system operations']
---
<Warning>**Restoring a snapshot requires you to trust the snapshot provider.** A malicious or compromised provider could corrupt a snapshot in ways that are not immediately detectable. Your node cannot verify the historical state in a snapshot at all. For safe bootstrapping, use [state sync](/node/statesync). It is the only officially supported bootstrap method for Sei Mainnet.</Warning>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit] This warning is long and makes several points. Two <Warning> blocks in a row also weaken each other. Consider keeping only the bold sentence and the state sync recommendation here, and moving the detail about corrupted snapshots into body text.

@alexander-sei
alexander-sei merged commit ae5e368 into main Nov 20, 2026
17 of 18 checks passed
@alexander-sei
alexander-sei deleted the docs/snapshot-trust-warning branch November 20, 2026 17:21

This branch was successfully deployed

1 active deployment
staging — 3de79a43 Deployed Nov 20, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant