Running your own Validator

Here's a quick guide to get started validating Centrifuge Chain Amber or Flint testnets.

  1. Open the [Centrifuge Chain Portal ](]

  2. Create a new key pair for your validator – a stash account (Vanessa Stash in this example) that is holding the funds to be staked/bonded and can transfer them, and a separate controller account (Vanessa in this example) that will be able to switch between validating/nominating/chilling and can set session keys, which will be used for the validator tasks such as block proposals, finalization etc:

  3. Send tokens to your stash (for staking) and controller accounts (small amount to pay fees for actions) as described above. In order to become a validator, the stash account needs to own enough tokens to replace another validator in the next era.

  4. Head over to the staking screen and create a new stake

  5. Generate new session keys in your node's keystore by running: curl -H 'Content-Type: application/json' --data '{ "jsonrpc":"2.0", "method":"author_rotateKeys", "id": 1 }' This command will return the public keys under the "result" field starting with 0x....

  6. Set the session keys:

  7. You are ready to start validating! Change your status to validating by clicking "Validate":

  8. In the staking overview, you should now see your validator in the "Next Up" column: If validator slots are empty or if your validator has a higher stake bonded then an active validator, it will enter the validator set at the next era change (at most in 24 hours on Amber/Flint):

  9. All done! If you want to stop validating, head back to "Account actions" and click "Stop Validating" You should now see that your validator is no longer selected for the next era (at most in 24 hours on Amber/Flint): After the next era change, your validator should go back to idling and no longer show up in the Staking overview: