Polkadot has executed the referendum setting a 500-validator limit, but the Relay Chain still listed 600 validators in the finalized block checked for this report. Referendum 1966 passed on November 8, 2026, and its designated enactment block arrived on November 10. Both governance interfaces marked the measure executed when checked on November 11.
The distinction is practical: changing a limit and rotating the active set are separate events. For people nominating DOT, the immediate question is whether their stake backs an elected validator after the smaller set takes effect. The vote alone does not establish that every existing nomination will keep earning rewards.
The vote and the validator election run on different clocks
SubSquare displayed approximately 48.14 million weighted DOT votes in favor and 36,388.1 against, with approval rounded to 99.9%. The referendum specified Relay Chain block 33,814,400 for enactment. Its on-chain timestamp was November 10 at 10:21:48 UTC. The proposal said the 500-seat limit would be reflected in the first era after execution.
At finalized Relay Chain block 33,822,487, however, the session-validator list still contained 600 entries. Polkadot's official chain-state reference listed 500. The direct block-specific reading is the more precise evidence for that snapshot; the documentation figure should not be mistaken for proof that the active-set rotation had already occurred.
A separate finalized Asset Hub check confirmed that the staking validator-count setting was 500. That block was timestamped November 10 at 23:51:12 UTC. Together, the readings distinguish an enacted configuration from the validator group actually serving the Relay Chain session.
That distinction matters because an era is the cycle used for staking elections and rewards. Polkadot's nominator documentation explains that the active assignment is recalculated for each era, roughly every 24 hours. A nomination submitted earlier is therefore not a permanent reservation for a validator seat.
The approved package also adjusts Relay Chain settings governing how many validators check each processing core, alongside Coretime configuration. These accompany the smaller set; the measure is more than deleting names from a list. Readers unfamiliar with the roles can start with the Polkadot network overview.
The reward budget shrinks alongside the set
A November 4 reward-design proposal explains the financial logic: the validator-incentive allocation falls from 22.6% to 18.8% of the Dynamic Allocation Pool budget at the first step. The difference stays in the pool's buffer. The intended effect is to keep the average budget per active validator slot broadly steady while paying for fewer slots.
That is a budget allocation change, not evidence that the same amount of DOT disappears from total issuance. Nor does an average budget promise a particular operator's payout. The proposal says validator rewards depend on self-stake and warns that payouts can temporarily dip while the new budget and the smaller elected set take effect at different times.
Current developer documentation makes another distinction relevant to nominators: validators receive a separate self-stake incentive, and their commission on nominator rewards is fixed at zero. The validator allocation should therefore not be treated as if it were a direct percentage cut to every nominator's reward.
Why the roadmap calls for fewer validators doing more work
The October 16 infrastructure roadmap argues that 600 validators exceed the network's needs. It connects a smaller set with a broader role for operators, called Metanodes, which would also support Asset Hub and People Chain and serve application access requests. Its stated goal is to align infrastructure spending with reliability and performance requirements.
The proposed sequence is 500, then 400, then 320 validators, with roughly a week between steps. The October roadmap targeted November; the November 4 discussion described completion before year-end. These are planning aims. Each later step needs its own governance process, including Fellowship whitelisting and a token-holder vote.
The staged approach is intended to leave room for monitoring and stopping if performance deteriorates. It does not demonstrate that a smaller set has already improved throughput or reliability. Those outcomes need measurements after the change.
Decentralization depends on who occupies the seats
Removing seats narrows the number of active positions available. The security consequence cannot be calculated from that count alone. Polkadot's election documentation emphasizes distributing backing across the elected set and maintaining proportional representation, so a simple ranking of current stake is not a reliable list of the next election's winners.
The trade-off deserves attention: a network can reduce its operating budget while leaving fewer opportunities for independent operators to participate actively. Whether that produces greater concentration depends on the resulting distribution of operators and stake. The referendum result does not answer that question by itself.
For nominators, the practical checks are more immediate:
- Review the current era's nomination status, especially whether any selected validator is actively backed by your stake.
- Distinguish a waiting validator, which was not elected, from an inactive nomination to a validator that was elected but is not receiving your stake.
- Check actual reward eligibility and payouts rather than assuming that a submitted nomination is enough.
The crypto staking guide explains the broader difference between delegating tokens and receiving rewards. The first era with 500 active validators was not established by the final chain-state check. That transition, followed by any separate proposals to reduce the set to 400 and 320, is the next development to verify.