I propose to increase the max collators by one which adds one more slot for collator candidates to become a collator.

Please note that the `join_candidates` extrinsic is still disabled such that you can only join via a referendum.

 Set the maximum number of collator candidates that can be selected
 at the beginning of each validation round.

 Changes are not applied until the start of the next round.

 The new value must be higher than the minimum allowed as set in the
 pallet's configuration.

 The dispatch origin must be Root.

 Emits `MaxSelectedCandidatesSet`.


 # <weight>
 - The transaction's complexity is mainly dependent on updating the
   `SelectedCandidates` storage in `select_top_candidates` which in
   return depends on the number of `MaxSelectedCandidates` (N).
 - For each N, we read `CollatorState` from the storage.
 ---------
 Weight: O(N) where N is `MaxSelectedCandidates` bounded by
 `MaxTopCandidates`
 - Reads: MaxSelectedCandidates, TopCandidates, N * CollatorState
 - Writes: MaxSelectedCandidates
 # </weight>

- They want to add one more slot for collator candidates to become a collator.
- You can only join as a collator candidate through a referendum.
- They are not allowing joining through the "join_candidates" extrinsic.
- This proposal is about making a change to the collator system.
- The purpose is to give more people the opportunity to become collators.

#0 Increase max collators by one (from 16 to 17)

No Active Proposals