Staking: Max nominators for each operator #2120
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces MaxNominators parameter to limit nominators per Operators.
Since we cannot use
CountedStorageNmap
to get the count with operatorId prefix, I introduced a new storage that tracks the nominator count for each operator. The count is tracked when there is a new nominator show intent to nominate or when a Nominator withdraws all the stake from an Operator.If MaxNominators are set to
0
, which is a requirement for Stake wars, this will not allow any nominators for any operators and can be changed through a runtime upgrade.cc: @jfrank-summit
Code contributor checklist: