Crate pallet_committee_management

Ban logic

In case of insufficient validator’s uptime, we need to remove such validators from the committee, so that the network is as healthy as possible. This is achieved by calculating number of underperformance sessions, which means that number of blocks produced by the validator is less than some predefined threshold. In other words, if a validator:

• performance in a session is less or equal to a configurable threshold BanConfig::minimal_expected_performance (from 0 to 100%), and,
• it happened at least BanConfig::underperformed_session_count_threshold times, then the validator is considered an underperformer and hence removed (ie banned out) from the committee.

Thresholds

There are two ban thresholds described above, see BanConfig.

Next era vs current era

Current and next era have distinct thresholds values, as we calculate bans during the start of the new era. They follow the same logic as next era committee seats: at the time of planning the first session of next the era, next values become current ones.

Re-exports

• pub use pallet::*;

Modules

• impls 🔒
• manager 🔒
• pallet
  The pallet module in each FRAME pallet hosts the most important items needed to construct this pallet.
• traits 🔒

Structs

• CurrentAndNextSessionValidators 🔒
• DefaultLenientThreshold
• SessionAndEraManager
  SessionManager that also fires EraManager functions. It is responsible for rotation of the committee, bans and rewards logic.
• ValidatorTotalRewards

Constants

• LOG_TARGET 🔒
• STORAGE_VERSION 🔒

Traits

• EraInfoProvider
• ValidatorExtractor
• ValidatorRewardsHandler

Type Aliases

• TotalReward