How many active validators does a Polkadot nominator actually need?

Polkadot lets a nominator approve as many as 16 validator candidates. In practice, that allowance is often treated as a 16-deep list of incumbent backups: choose as many validators from the current active set as possible so that at least one pays in the forthcoming era.

The election system does not require that strategy. Sixteen is a bound on the degree of the nomination graph, not a protocol estimate of how many active validators are needed for reward continuity. For an electing nominator, one nominated winner is sufficient for the election to assign the nominator's stake. The remaining approvals can therefore do useful work: help credible waiting validators enter the set and broaden the operator base that secures Polkadot.

Recommendation

• Use five active nominations: currently elected validators from distinct operators and, preferably, different infrastructure failure domains.
• Use the other eleven nominations as a Growth Slate: credible waiting validators selected to help new candidates enter the active set and, where possible, broaden operator participation.

Together, these form a 16-target slate with two distinct roles. The five active nominations provide modeled next-era assignment coverage. The eleven Growth Slate nominations use the remaining capacity to support validator-set renewal, with most positions intended to broaden operator participation.

Under the current 600-seat, 724-candidate geometry, four active nominations provide 99.8245% modeled next-era assignment coverage. Five raise that figure to 99.9647% and are the first count to clear the 99.9% policy threshold.

It is important to note that no five validators selected from the current active set are guaranteed to remain elected next era. Active nominations describes their status at the time of selection.

How nominations and assignments work

Polkadot nominations are approval edges, not a ranked fallback queue. Sequential Phragmén elects a committee and returns assignments only along edges to elected candidates. If one or more of a nominator's targets are elected, the assignment weights across those winners are normalized to the nominator's full stake.

Consequently:

• if none of the nominator's targets is elected, it receives no active election assignment;
• if at least one target is elected, its stake is assigned across one or more elected targets; and
• adding a waiting target does not reserve one-sixteenth of the stake or dilute the stake away from winners.

This follows from the Sequential Phragmén implementation and the subsequent balancing and edge-reduction process described in the Polkadot NPoS documentation.

This distinction is the foundation of the proposal. Extra targets hedge against uncertainty about which candidates win; they do not split the original stake into equal tranches. A waiting approval does not mechanically reserve one-sixteenth of the stake; conditional on another selected target winning, the voter remains assignable. The earlier technical discussion of a dynamic nomination quota describes this bootstrapping property explicitly: multiple nominations let voters support new validators while retaining exposure when at least one target is selected (Polkadot Forum).

There are two important conditions. First, the nominator must be included in the bounded election voter snapshot. Second, an assignment is reward eligibility, not a promise of a positive daily payout: the elected validator must perform and earn era points, and payout processing must occur.

Methodology: deriving the minimum active-nomination count

Define:

• T = 724, the number of registered candidates;
• W = 600, the number of elected validators and therefore the size of each active set;
• d, the number of currently active validators not re-elected at the next election; and
• k, the number of currently active validators nominated by the wallet.

Under the fixed-candidate-universe assumption, the current and next active sets each contain W validators drawn from the same T candidates. Two key facts follow:

• At least 476 validators remain active: the two sets must overlap by at least 2W − T = 476 validators.
• At most 124 current validators become waiting: no more than T − W = 124 can miss re-election, so d ranges from 0 to 124.

For a diversified wallet, the model treats its k active nominations as a uniform sample without replacement from the W current validators. Looking only at this active-nomination core, next-era coverage fails when none of the k selections is re-elected.

The calculation uses W, d and k to compare the number of possible nomination groups with the number that would fail; C(n, r) denotes the number of unique groups of r items chosen from a pool of n.

• C(W, k) counts all possible groups of k nominations from the W current validators.
• C(d, k) counts the groups in which all k nominations are among the d validators not re-elected.

The failure probability is the second count divided by the first:

Success means that at least one of the k nominated validators is re-elected, so its probability is the complement of failure:

The table reports this success probability as modeled coverage. Because failure increases with d, the conservative fixed-universe case sets d = 124. Evaluating different values of k then gives:

Active nominations	Failure probability	Modeled next-era coverage
3	0.8658%	99.1342%
4	0.1755%	99.8245%
5	0.0353%	99.9647%
6	0.0071%	99.9929%
7	0.0014%	99.9986%
8	0.0003%	99.9997%

If one adopts a 99.9% one-era modeled-coverage policy threshold, five is the smallest qualifying count.

This model measures portfolio-level election risk; it does not assume that NPoS selects validators randomly. Election winners are determined by backing and the election objective. Selecting several validators from the same operator or infrastructure provider does not change that process. It can, however, make the uniform-sampling benchmark less representative if those validators have correlated chances of leaving the active set. Operator and infrastructure deduplication is therefore a portfolio-resilience recommendation, not an election requirement.

Nor is there a deterministic guarantee. Any specified set of up to 124 current validators could theoretically miss re-election. A pigeonhole guarantee under the current geometry would require 125 current-active targets—far above the quota. This is why “definitely active” overstates what the chain can promise.

Testing five active nominees over recent eras

The 600-validator active set was reconstructed from Staking.ErasStakersOverview for eras 2180–2263, an 84-era history window ending at the reference block.

The observed era-to-era validator turnover is summarized below:

Era-to-era replacements	Validators out of 600
Mean	8.37
Median	5
Maximum	67

The maximum occurred during the June 2026 forced-chill and election-stall period, when 67 elected validators below the new self-stake threshold were removed from the candidate set. That incident is documented in the staking election post-mortem.

Each rolling 30-era window was evaluated to determine the exact probability that a uniformly diversified, static set of active nominations would have at least one era in which all of its nominees were absent from the active set. These are active-nomination-only results; the rest of the Growth Slate can also become elected and improve total coverage.

Static active nominations	Average 30-era lapse probability	Worst observed 30-era lapse probability
5	0.0231%	0.1603%
6	0.0048%	0.0430%
7	0.0010%	0.0115%

Across the full 83-transition span, the corresponding exact lapse probabilities for static sets of five, six and seven active nominations were 0.4127%, 0.1247% and 0.0371%.

The resulting policy tiers are:

• Five active nominations with monthly review: the practical default, with 99.9647% modeled next-era coverage and 99.9769% average active-nomination-only continuity across historical 30-era windows.
• Six active nominations: the conservative choice for a wallet that wants the worst observed rolling-month active-nomination-only result to exceed 99.9%.
• Seven active nominations: appropriate when a portfolio may remain untouched for roughly a quarter.

The recommendation in this paper is five currently active nominations for a slate reviewed monthly. Reclassify the slate:

• monthly;
• immediately after a mass chill;
• immediately after a material change to the validator count; or
• immediately after a major staking-parameter referendum.

Operationally, a wallet should prepare changes before the relevant era boundary. The current runtime begins planning the following election as soon as an era starts; a status seen later in the era may be too late for the snapshot already being built (runtime planning configuration).

The Growth Slate

The remaining eleven targets should collectively be called the Growth Slate. They should be waiting—meaning registered but not currently elected—at the time of selection. If a qualifying validator is already elected, it belongs within the active-nomination allocation rather than the Growth Slate.

All Growth Slate candidates should first pass baseline filters: valid current keys and registration, required self-stake, acceptable performance when measurable, identifiable control, and no unacceptable common infrastructure or ownership concentration. The current Polkadot staking model has enforced 0% validator commission and a validator self-stake incentive since era 2220, making commission an obsolete differentiator on Polkadot (Referendum 1909 summary).

Candidate group recommendations

After applying the baseline filters, select Growth Slate candidates from three recommended groups: operator-level reward retainment, validator-level self-stake growth, or continuity within an already trusted operator.

1. Retainment Leaders

Question: Does the operator's publicly linked identity graph tend to retain the DOT earned through validation?

The retainment rate measures how much of an operator identity graph's validation rewards remain in its publicly linked balances over a month. It takes the graph's positive balance increase, caps it at the rewards earned during the period, and divides by those rewards.

Recommended qualification:

• while only two completed periods exist, both valid months must have at least 75% retainment; and
• once three or more clean periods exist, use a rolling three-month median of at least 75%, with no month below 50%;

Seventy-five percent is a proposed wallet-UX threshold. It allows for operating costs estimated at roughly 7% of the rewards earned by a validator active for a full month, together with leeway for team expenses, while expecting most rewards to remain within the operator's public identity graph.

Rationale: retainment is the broadest on-chain alignment signal. It recognizes rewards held in publicly linked liquid, reserved or validator accounts rather than requiring every retained DOT to be self-staked.

2. Self-Stake Builders

Question: Does this particular validator turn its rewards into additional slashable self-stake?

The compound rate applies the same capped calculation to a validator's self-stake: take the positive increase in self-stake, cap it at the validator's own rewards for the period, and divide by those rewards.

Recommended qualification:

• apply the same two-period and rolling three-month 75% persistence tests used for Retainment Leaders;

Rationale: compounding is narrower than retainment and directly measures increased validator self-stake. It aligns with Polkadot's current incentive model, in which validators—not nominators—retain slash exposure. A waiting candidate needs prior elected periods to have a meaningful reward denominator; a never-elected validator cannot manufacture a valid compound rate.

3. Operator Continuity Bench

Question: Is there a credible waiting sibling from an operator that the nominator already trusts?

Recommended qualification:

• the candidate is waiting and shares verified control with an already represented operator;
• the operator recorded at least 50% retainment in each of the last two valid months, and in each of the last three once sufficient history exists; and
• allocate no more than two Growth Slate positions to this category.

Rationale: this supports operational continuity and gives a trusted operator another route into the set. The 50% rule is a proposed majority-retainment floor, not a definition of “high” or a performance guarantee. This category does not increase operator decentralisation; it extends existing trust to another validator controlled by the same operator.

Deduplication rules

These three categories must be mutually exclusive for slot accounting.

1. Resolve common control before assigning a category using the People Chain identity graph and disclosed ownership. Public identity links are a lower bound on common control, not proof of independent control.
2. Count retainment once per identity graph. Sibling validators inherit the same graph-level observation.
3. Prefer operators with fewer elected validators when candidates are otherwise comparable.

Compounding can itself increase graph retainment, so the two rates are complementary views—not statistically independent factors that should be multiplied into a score. Both methods and their limitations are set out in “Introducing validator retainment and compound rates”.

A practical 16-target slate

The following is a target allocation using the above three candidate groups. The five active nominations are the first priority; the remaining eleven are a Growth Slate of waiting candidates:

Slate component	Target count
Currently active nominations—five distinct operators	5
Retainment Leaders—waiting, distinct operators	5
Self-Stake Builders—waiting, distinct operators	4
Operator Continuity Bench	Up to 2
Total	16

If a candidate qualifies under both independent-operator metrics, place it where the eligible supply is thinner and retain the Dual-Signal badge. If any category has fewer eligible candidates than its target, shift those positions to distinct-operator candidates from another evidence-based waiting cohort; do not weaken the thresholds merely to fill all 16.

Limitations

The recommendation is subject to several important limitations:

1. Five is a model-dependent policy choice. It is the smallest count above the chosen 99.9% coverage threshold under the current 724-candidate, 600-seat geometry—not a permanent protocol constant.
2. The uniform-sampling model is not an election forecast. Named validators have different backing and may have correlated chances of leaving the active set, so actual portfolio outcomes can differ from the benchmark.
3. The fixed-candidate-universe assumption can break. Candidates can register, chill or change eligibility between elections. The active-versus-waiting classification must therefore be reviewed regularly and after material staking changes.
4. Active assignment is not payout certainty. Snapshot inclusion, validator performance, era points and payout processing remain necessary.
5. Growth Slate nominations do not guarantee entry or decentralisation. A waiting validator may remain unelected, and an Operator Continuity Bench selection extends an existing operator relationship rather than broadening operator representation.
6. Retainment and compound rates are balance-change proxies. External deposits, operating costs, taxes, unlinked accounts and intra-month transfers can affect them; the measures do not trace individual DOT and may overlap.
7. Identity and metric evidence is incomplete. Public identity links may not reveal all common control, and the available history is short and crosses the June–July 2026 staking-policy regime change. Early classifications should remain provisional.

Conclusion

The 16-slot nomination maximum is not an estimate of how many active nominations are required. Under current Polkadot conditions, the evidence supports five diversified active nominations as the managed default. Five is the first count above a 99.9% modeled next-era coverage threshold; a sixth is a reasonable conservative option for less frequently managed portfolios.

The remaining targets should not imitate the first five. They should be a Growth Slate: waiting validators selected through transparent evidence of operator-level retainment, validator-level self-stake building, or explicitly labeled operator continuity.

The broader principle is durable even when the number changes: use only as many incumbent nominations as the desired continuity target requires, and make every remaining approval compete for the future validator set.

Methodology and reproducibility notes

• Network: Polkadot Asset Hub, public WebSocket RPC.
• Reference block: 19,493,000; hash 0xf3af2d21657faad94b8e7b162f7fe0d9a5fd7eabb79292806e0ac9296c980830.
• Active-set classification: validator keys in Staking.ErasStakersOverview(2263, validator).
• Candidate classification: keys in Staking.Validators.
• Historical sets: Staking.ErasStakersOverview keys for eras 2180–2263.
• Historical lapse calculation: within each rolling 30-era window, a static group of k nominations is counted as failing if all k validators are absent in any era. The number of unique failing groups is divided by C(600, k), the number of all possible groups. Inclusion–exclusion ensures that a group failing in multiple eras is counted only once, producing an exact probability rather than a simulation.
• Percentages are rounded; calculations used unrounded counts.