Skip to content
Merged
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
18 changes: 17 additions & 1 deletion docs/maintain/maintain-guides-how-to-validate-polkadot.md
Original file line number Diff line number Diff line change
Expand Up @@ -370,7 +370,7 @@ You can begin syncing your node by running the following command if you do not w
validator mode right away:

```sh
./target/release/polkadot
./target/production/polkadot
```

```
Expand Down Expand Up @@ -401,6 +401,22 @@ validator mode right away:

:::

:::tip Use Warp sync for faster syncing

By default, the node performs `full` sync, which downloads and validates the full blockchain
history. `warp` sync can be used as a faster way to sync the validator node.

`./target/production/polkadot --sync warp`

Warp sync initially downloads and validates the finality proofs from [GRANDPA](../learn/learn-consensus.md#finality-gadget-grandpa)
and then downloads the state of the latest finalized block. After the warp sync, the node is ready to
import the latest blocks from the network and can be used as a Validator. The blocks from genesis
will be downloaded in the background. Check
[this discussion](https://substrate.stackexchange.com/questions/334/what-kinds-of-sync-mechanisms-does-substrate-implement/)
for more information about the different sync options available.

:::

:::note Validators should sync using the RocksDb backend

This is implicit by default, but can be explicit by passing the `--database RocksDb` flag.
Expand Down