Repository navigation
fix: warn that provider snapshots require trusting the provider - #23
alexander-sei wants to merge 2 commits into
Conversation
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>
PR SummaryLow Risk Reviewed by Cursor Bugbot for commit a1d9f41. Bugbot is set up for automated code reviews on this repo. Configure here. |
There was a problem hiding this comment.
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>
|
@seidroid review |
There was a problem hiding this comment.
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.
Why
node-operations.mdtold agents to "Bootstrap via state sync (below) or a snapshot", andresources.mdlisted Polkachu snapshots with no caveat. Agents repeat that as an equal alternative to state sync. The generatedsei-nodesskill 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
ecosystem/node-operations.mdresources.mdVerification
git merge-treeagainst the open PRs that touchnode-operations.md(skills: v6.6.4 and v6.7.1–v6.7.4 catch-up #20, skills: v6.7.0 catch-up #21, skills: v6.8.0 catch-up #22). All three merge cleanly. The new section sits after the---that closes the State Sync section, so it doesn't collide with the Trust period subsection that skills: v6.6.4 and v6.7.1–v6.7.4 catch-up #20 adds.SKILL*.mdlinks change. No frontmatter touched, so trigger behaviour is unchanged.After this merges, run Sync agent skills from sei-skill in sei-docs to regenerate
.mintlify/skills/sei-nodes/SKILL.md.Made with Cursor