Skip to content

fix: warn that provider snapshots require trusting the provider - #23

Open
alexander-sei wants to merge 2 commits into
mainfrom
fix/snapshot-trust-warning
Open

alexander-sei wants to merge 2 commits into
mainfrom
fix/snapshot-trust-warning

Conversation

@alexander-sei

Copy link
Copy Markdown
Contributor

Why

node-operations.md told agents to "Bootstrap via state sync (below) or a snapshot", and resources.md listed Polkachu snapshots with no caveat. Agents repeat that as an equal alternative to state sync. The generated sei-nodes skill on docs.sei.io currently says: "Alternative bootstrap: restore a provider snapshot into $HOME/.sei".

That isn't the supported path. Restoring a provider snapshot means trusting the provider: a malicious or compromised provider can corrupt a snapshot in ways that are not immediately detectable, and the node cannot verify the historical State Store (SS) data in it at all. State sync is the only officially supported bootstrap method for Sei Mainnet.

Docs counterpart: sei-protocol/sei-docs#110 adds the same warning to https://docs.sei.io/node/snapshot.

Changes

File What
ecosystem/node-operations.md The genesis note now points at state sync and calls a provider snapshot a fallback that requires trusting the provider. The State Sync intro says it is the only officially supported bootstrap method for Sei Mainnet. A new Provider Snapshots (Trust Required) section explains why a snapshot needs trust and tells agents to suggest one only when state sync can't do the job (for example, an archive node), always with the trust caveat and a link to the docs procedure.
resources.md The Polkachu snapshots row is flagged inline, matching the style used for the retired Oracle precompile.

Verification

After this merges, run Sync agent skills from sei-skill in sei-docs to regenerate .mintlify/skills/sei-nodes/SKILL.md.

Made with Cursor

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 <cursoragent@cursor.com>
@cursor

cursor Bot commented Nov 20, 2026 •

Copy link
Copy Markdown

PR Summary

Low Risk
Documentation-only changes to agent skill references; no runtime or security-sensitive code paths.

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

seidroid[bot]
seidroid Bot previously approved these changes Nov 20, 2026

@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 accurate trust caveats for provider snapshots and makes state sync the recommended bootstrap path. It touches no frontmatter and no reference links. One small fix is suggested: the archive-node guidance should require a snapshot that keeps full history.

Findings: 0 blocking | 1 non-blocking | 1 posted inline

Blockers

  • None at the file/PR level.

Non-blocking

  • None at the file/PR level.
  • 1 suggestion(s)/nit(s) flagged inline on specific lines.

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 <cursoragent@cursor.com>
@alexander-sei

Copy link
Copy Markdown
Contributor Author

@seidroid review

@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 docs-only change says provider snapshots require trusting the provider and makes state sync the recommended way to bootstrap a node. It also includes the earlier fix that archive nodes need an archive (unpruned) snapshot. It adds or moves no reference files and does not touch frontmatter, and I found nothing else to raise.

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

Blockers

  • None at the file/PR level.

Non-blocking

  • None at the file/PR level.

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