Repository navigation
docs(node): warn that snapshots require trusting the provider #110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4,6 +4,8 @@ sidebarTitle: 'Snapshot Sync' | |
| 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> | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [nit] This warning is long and makes several points. Two |
||
|
|
||
| <Warning>Before you resync a node from a snapshot, make sure that your validator cannot double sign. After a successful resync, your validator must _under no circumstance_ double sign blocks at previous heights. If it does, the validator is tombstoned.</Warning> | ||
|
|
||
| Use snapshot sync to start a new full node and join an existing network quickly. Snapshot sync restores the node from a snapshot instead of replaying all historical blocks. | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
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_heightandtrust_hashit uses come from the configured RPC endpoint (seenode/statesync.mdxaround 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.)