2 posts tagged with "NPoS"

Polkadot should reduce the maximum number of validators a nominator can approve from sixteen to eight. Eight offers room for a resilient selection of active validators and additional choices, while narrowing the breadth of continuing support for accounts subject to that limit. The proposed transition would preserve existing longer lists, with their allowances decreasing as targets are removed. The objective is a more natural flow of support between validators, with informed nominator choices giving credible candidates a realistic route into the active set.

The case rests on two findings. Recently submitted full nomination lists overwhelmingly cover established winners, and the additional coverage available from very long lists has diminishing value in a mathematical continuity benchmark. Persistent nomination preferences also provide substantial backing to a subset of incumbents. Together, these findings justify reconsidering whether sixteen is an appropriate default allowance.

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.