Skip to content

Commit 2fb4ca0

Browse files
committed
docs/node/run-your-node: Add a tips about state sync
Following those tips prevents (unlikely) long range attacks.
1 parent 98ae6a8 commit 2fb4ca0

1 file changed

Lines changed: 16 additions & 0 deletions

File tree

docs/node/run-your-node/advanced/sync-node-using-state-sync.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,15 @@ to be able to [detect and submit evidence for a light client attack].
2323

2424
:::
2525

26+
:::tip
27+
28+
After a successful state sync it is always recommended to manually check if you
29+
see the same chain as others. This can be done by comparing block hash at
30+
a recent height with sources that you trust: e.g. your own nodes, trusted nodes
31+
from external entity, block explorers, etc.
32+
33+
:::
34+
2635
To configure your node to use the state sync, amend your node's configuration
2736
(i.e. `config.yml`) with (non-relevant fields omitted):
2837

@@ -93,6 +102,13 @@ configuring the trusted height and hash for the block that is around 10 days old
93102

94103
:::
95104

105+
:::tip
106+
107+
If using centralized or untrusted sources it is always recommended to
108+
fetch and compare data from multiple sources.
109+
110+
:::
111+
96112
#### Block Explorers
97113

98114
Browse to one of our block explorers (e.g. [Oasis Explorer], [Oasis Scan]) and

0 commit comments

Comments
 (0)