Перейти к основному содержимому

How to Upgrade Your Validator

Validators perform critical functions for the network, and as such, have strict uptime requirements. Validators may have to go offline for periods of time to upgrade the client software or the host machine. Usually, standard upgrades will only require you to stop your server, replace the binary and spin it up again. Validators may also need to perform maintenance, such as resizing a disk, where you cannot continue running the node on the current server. This guide will walk you through upgrading your machine and keeping your validator online.

The process can take several hours, so make sure you understand the instructions first and plan accordingly.

Note: keep an eye out on new releases from the community and upgrade/downgrade accordingly.

Key Components#

Session Keys#

Session keys are stored in the client and used to sign validator operations. They are what link your validator node to your Controller account. You cannot change them mid-Session.

More info about keys in Polkadot.


Validators keep a database with all of their votes. If two machines have the same Session keys but different databases, they risk equivocating. For this reason, we will generate new Session keys each time we change machines.

More info about equivocation.


You will need to start a second validator to operate while you upgrade your primary. Throughout these steps, we will refer to the validator that you are upgrading as "Validator A" and the second one as "Validator B."

Session N#

  1. Start a second node. Once it is synced, use the --validator flag. This is "Validator B."
  2. Generate Session keys in Validator B.
  3. Submit a set_key extrinsic from your Controller account with your new Session keys.
  4. Take note of the Session that this extrinsic was executed in.

It is imperative that your Validator A keep running in this Session. set_key only takes effect in the next Session.

Session N+1#

Validator B is now acting as your validator. You can safely take Validator A offline. See note at bottom.

  1. Stop Validator A.
  2. Perform your system or client upgrade.
  3. Start Validator A and sync the database.
  4. Generate new Session keys in Validator A.
  5. Submit a set_key extrinsic from your Controller account with your new Session keys for Validator A.
  6. Take note of the Session that this extrinsic was executed in.

Again, it is imperative that Validator B keep running until the next Session.

Once the Session changes, Validator A will take over. You can safely stop Validator B.

NOTE: To verify that the Session has changed, make sure that a block in the new Session is finalized. You should see log messages like this to indicate the change:

2019-10-28 21:44:13 Applying authority set change scheduled at block #4500922019-10-28 21:44:13 Applying GRANDPA set change to new set with 20 authorities