Skip to content

Commit

Permalink
Add tips on node backup
Browse files Browse the repository at this point in the history
  • Loading branch information
navigaid committed Aug 18, 2023
1 parent ba075ea commit e6571c3
Showing 1 changed file with 14 additions and 0 deletions.
14 changes: 14 additions & 0 deletions docs/staking/validator-faqs.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -240,3 +240,17 @@ You can query the storage item by visiting [PolkadotJS Apps](https://polkadot.js
![querying chainstate](./img/querying-chainstate.png)

In each era, if there are more validators than the ideal threshold, the inactive validators will stay in the waiting list until they are elected.

## What files should I backup before migrating the validator node to another machine?

It is crucial to have backups of the following files and directories in case your current node becomes inaccessible due to extreme conditions:

1. __Validator Session Keys__: If you are running a validator node, it is recommended to backup your session keys. These files are typically located in the `~/.local/share/gear/chains/vara_network/keystore` directory.

2. __Network Key__: The network key uniquely identifies your node in the peer-to-peer network. It is located at `~/.local/share/gear/chains/vara_network/network/secret_ed25519`.

3. __Blockchain Database__(optional): The blockchain database resides in the `~/.local/share/gear/chains/vara_network/db` directory. It can be deleted and synchronized from scratch at any time, but keep in mind that this process may take some time.

:::info
Make sure the old node is stopped before you launch the new node, otherwise you may get slashed for equivocation.
:::

0 comments on commit e6571c3

Please sign in to comment.