Concepts
Validator Network
Validator Types & States

Validator Types & States

This page is intended to explain what the different states of a Validator are possible in the Chainflip system, and what each of them means.

It is important to note that a Validator does not refer to just any node on the Chainflip State Chain network. In contrast to State Chain Client operators, who may be using them for liquidity management, running a Broker, or simply monitoring the State Chain for data, a Validator, a node must also run the Chainflip Engine (CFE) sidecar module and have configured endpoints for all external chains, as well as set their State Chain account type to Validator.

This page should help operators understand how to set their Validator state to participate in auctions and manage their system accordingly.


Status TagDescriptionCriteria
QualifiedA Qualified validator can participate in Auctions.

A validator node is considered Qualified if all of the following conditions are fulfilled:

  • Account Role is Validator
  • Online (based on last heartbeat submission)
  • Session Keys are registered
  • Peer Id is registered
  • Validator is not serving a suspension because of recently failing authorship
  • It is running at least the minimum required version of the Chainflip Engine
BiddingA bidding node is indicating its intention to participate in auction.
Validators that wish to participate should set their bidding intention to true

Outside of auction periods, Validators can set their bidding status freely.

During Auctions:

  • Bidding Validators may not redeem any funds and may not change their state to Non-Bidding.
  • All Validators can add funds at any time
RetiringA retiring validator is indicating its intention to retire from the next auction.
Validators that wish to retire should set their bidding intention to false (non-bidding).

Outside of auction periods, Validators can set their bidding status freely.

During Auctions:

  • Non-Bidding Validators can redeem any unlocked funds and can change their state to bidding.
  • All Validators can add funds at any time
BackupA Backup validator earns FLIP rewards but does not participate in block authorship. See Backup Rewards section.

May be a keyholder.
  • Is Qualified
  • Is not an Authority
  • Is among the set of highest bidding Non-Authorities, (maximum 1/3rd the size of the current Authority Set, usually 50).
KeyholderA Keyholder holds a fragment of an unexpired threshold signing key from a previous Authority Set.
  • A node remains as Keyholder until all held key fragments expire. Keys expire at the start of the epoch after the next.
  • Keyholders can redeem funds if they are not bidding
Authority

Authorities are responsible for block authorship and consensus, witnessing, threshold signing and transaction broadcasting. In return they earn Authority Rewards


Authorities are Bonded according to the auction preceding the KeyGen ceremony for the held key.

  • Auction winner
  • Successfully participated in a Keygen ceremony.
  • Block Producer & State Chain Authority
  • Witnesser