collator_selection

Branch/Release: release-polkadot-v1.10.0

Source Code

Purpose

This pallet is needed to manage the set of collators for each session and to provision the next session with the actual list of collators.

Config

  • Pallet-specific configs

    • UpdateOrigin — defines the list of origins that are able to modify the settings of collators (e.g. set and remove list of invulnerables, desired candidates, candidacy bond). This type should implement the trait EnsureOrigin.

    • PotId — id of account that will hold a Pot.

    • MaxCandidates — maximum number of candidates

    • MinEligibleCollators — minimum number of collators to collect for the session

    • MaxInvulnerables — maximum number of invulnerables

    • KickThreshold — number of blocks that should pass since the last block produced by a candidate collator for it to be removed from a candidates list and not participate in collation for the next session.

    • ValidatorId — type for validator id

    • ValidatorIdOf — type that allows to convert AccountId to ValidatorId

    • ValidatorRegistration — type that checks that AccountId has its validator keys registered.

  • Common configs:

    • RuntimeEvent

    • Currency

    • WeightInfo

Dispatchables

set_invulnerables

pub fn set_invulnerables(new: Vec<T::AccountId>)

Sets a new list of invulnerable collators. The call must be signed and origin of the call must fulfill the EnsureOrigin check.

This call does not maintain the mutual exclusiveness of candidates and invulnerables lists.

Params:

  • new: Vec<T::AccountId> — a list of AccountIds of new invulnerables

Errors:

  • BadOrigin — caller’s origin does not fulfill the Config::EnsureOrigin check.

  • TooFewEligibleCollators — empty list of invulnerables was submitted and the number of candidates is smaller than Config::MinEligibleCollators

  • TooManyInvulnerables — submitted list length is longer than Config::MaxInvulnerables

Events:

  • InvalidInvulnerableSkipped(account_id) — submitted invulnerable does not have validator key or it is not registered

  • NewInvulnerables(invulnerables) — new invulnerable list was set

set_desired_candidates

pub fn set_desired_candidates(max: u32)

Set a new maximum possible number of candidates. If it is higher than Config::MaxCandidates, you should consider to rerun the benchmarks. The caller’s origin should fulfill the Config::EnsureOrigin check.

Params:

  • max: u32 — new desired candidates number

Errors:

  • BadOrigin — caller’s origin does not fulfill the Config::EnsureOrigin check.

Events:

  • NewDesiredCandidates(desired_candidates)

set_candidacy_bond

pub fn set_candidacy_bond(max: u32)

Set the amount for the deposit to be a candidate for collator.

Params:

  • bond: u32 — new amount for candidate deposit

Errors:

  • BadOrigin — caller’s origin does not fulfill the Config::EnsureOrigin check.

Events:

  • NewCandidacyBond(bond_amount)

register_as_candidate

pub fn register_as_candidate()

Register the caller as a collator candidate. Caller should be signed, have registered session keys and have amount needed for candidacy bond deposit. If successful, candidate will participate in collation process starting from the next session.

Errors:

  • BadOrigin — call is not signed

  • TooManyCandidates — number of collators is already at its maximum (specified in desired_candidates getter)

  • AlreadyInvulnerable — caller is already in invulnerable collators list, it does not need to be a candidate to become a collator

  • NoAssociatedValidatorId — caller does not have a session key.

  • ValidatorNotRegistered — caller session key is not registered

  • AlreadyCandidate — caller is already in candidates list

  • InsufficientBalance — candidate does not have enough funds for deposit for candidacy bond

  • LiquidityRestrictions — account restrictions (like frozen funds or vesting) prevent from creating a deposit

  • Overflow — reserved funds overflow the currency type. Should not happen in usual scenarios.

Events:

  • CandidateAdded(account_id, deposit)

leave_intent

pub fn leave_intent()

Unregister the caller from being a collator candidate. If successful, deposit will be returned and during the next session change collator will no longer participate in collation process. This call must be signed.

Errors:

  • BadOrigin — call is not signed

  • TooFewEligibleCollators — the number of collators for the next session will be less than Config::MinEligibleCollators in case of unregistration so the process is stopped.

  • NotCandidate — caller is not on candidate list, nothing to unregister

Events:

  • CandidateRemoved(account_id)

add_invulnerable

pub fn add_invulnerable(who: T::AccountId)

Add a new invulnerable. Call must be signed and caller pass Config::EnsureOrigin check. If a new invulnerable was previously a candidate, it will be removed from them.

Params:

  • who: T::AccountId — an account to add to invulnerables list

Errors:

  • BadOrigin — caller’s origin does not fulfill the Config::EnsureOrigin check.

  • NoAssociatedValidatorId — new invulnerable does not have a session key.

  • ValidatorNotRegistered — new invulnerable session key is not registered

  • AlreadyInvulnerable — caller is already in invulnerable collators list

Events:

  • InvulnerableAdded(account_id)

remove_invulnerable

pub fn remove_invulnerable(who: T::AccountId)

Remove an invulnerable from the list. Call must be signed and caller pass Config::EnsureOrigin check.

Params:

  • who: T::AccountId — an account to add to invulnerables list

Errors:

  • BadOrigin — caller’s origin does not fulfill the Config::EnsureOrigin check.

  • TooFewEligibleCollators — the number of invulnerable will become less than Config::MinEligibleCollators after the removal.

  • NotInvulnerable — the who is not an invulnerable

Events:

  • InvulnerableRemoved(account_id)

update_bond

pub fn update_bond(new_deposit: BalanceOf<T>)

Update the candidacy bond of origin to the new value.

Params:

  • new_deposit: BalanceOf<T> — new value for the candidacy bond

Errors:

  • BadOrigin — caller’s origin does not fulfill the Config::EnsureOrigin check.

  • DepositTooLow - new deposit is smaller than required candidacy bond.

  • NotCandidate - caller’s origin is not a candidate

  • IdenticalDeposit - deposit have not changed

  • InsufficientBalance — candidate does not have enough funds for deposit for candidacy bond

  • LiquidityRestrictions — account restrictions (like frozen funds or vesting) prevent from creating a deposit

  • Overflow — reserved funds overflow the currency type. Should not happen in usual scenarios.

  • InvalidUnreserve - after the unreserve the number of candidates becomes less than desired.

  • InsertToCandidateListFailed - candidate list is at maximum capacity. Should not happen in usual scenarios. Chain is misconfigured.

Events:

  • CandidateBondUpdated(account_id, deposit)

take_candidate_slot

pub fn take_candidate_slot(
	deposit: BalanceOf<T>,
	target: T::AccountId,
)

Try to replace the target’s candidacy by making a bigger candidacy bond.

Params:

  • deposit: BalanceOf<T> — value for the candidacy bond

  • target: T::AccountId - target candidate to replace

Errors:

  • BadOrigin — caller’s origin does not fulfill the Config::EnsureOrigin check.

  • AlreadyInvulnerable — caller is already in invulnerable collators list.

  • InsufficientBond - the deposit is less the candidacy bond or target’s deposit.

  • NoAssociatedValidatorId — caller does not have a session key.

  • ValidatorNotRegistered — caller session key is not registered.

  • AlreadyCandidate — caller is already in candidates list.

  • TargetIsNotCandidate - target is not in candidate list.

  • InsufficientBalance — candidate does not have enough funds for deposit for candidacy bond

  • LiquidityRestrictions — account restrictions (like frozen funds or vesting) prevent from creating a deposit

  • Overflow — reserved funds overflow the currency type. Should not happen in usual scenarios.

Events:

  • CandidateReplaced(old, new, deposit)

← XCM Executor
cumulus_pallet_aura_ext →