Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions node/snapshot.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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>

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.)

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.


<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.
Expand Down
4 changes: 2 additions & 2 deletions node/troubleshooting.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@
top -p $(pgrep seid)
```

## AppHash mismatch errors

Check warning on line 87 in node/troubleshooting.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/troubleshooting.mdx#L87

Use sentence case for headings: 'AppHash mismatch errors'.

If you get an AppHash mismatch, capture the state to compare it with a known-good version:

Expand Down Expand Up @@ -184,7 +184,7 @@

When you report a problem, always include the app hash, commit hash, and block height from your logs.

### Identifying AppHash errors

Check warning on line 187 in node/troubleshooting.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/troubleshooting.mdx#L187

Use sentence case for headings: 'Identifying AppHash errors'.

In logs, AppHash errors usually look like this:

Expand All @@ -204,9 +204,9 @@

1. **Stop the node immediately.**
2. **Try a node rollback first.** See [Node rollback](/node/troubleshooting#node-rollback).
3. **If the rollback fails, restore from a fresh snapshot:**
3. **If the rollback fails, resync the node:**

- Download a recent snapshot from trusted providers (Polkachu, PublicNode)
- Use [state sync](/node/statesync), or a recent [snapshot](/node/snapshot) from a provider that you trust
- Make sure that you use the correct node version
- Verify that peer configurations are up to date

Expand Down
Loading