Including contextual information form the staking team below - original discussion post <a href="../post/1224">HERE</a>.&nbsp;
___________________________________________________________________________
&nbsp;
Nomination pools are just around the corner for Polkadot, and this suggests some changes to be applied to the staking system.
First, let&rsquo;s recap on the current status quo: Currently, nominators can freely set their intention to nominate in Polkadot, as long as they meet two limits: a minimum of 10 DOTs is staked, and a maximum of 50_000 nominators is not filled. This creates a nomination market, where in every era, the top 22_500 nominators from this open market are chosen to participate in the election process, and possibly receive staking rewards (if other conditions like over-subscription are not met).
This is a complicated and involved process. Nomination pools are exactly here to combat this and provide a simpler experience for DOT-holders to participate in staking.
Based on this, let&rsquo;s cluster Polkadot nominators into two groups:&nbsp;active&nbsp;(in the top 22500), and&nbsp;waiting. The main concern at this point is to
<ul>
<li>Encourage all existing waiting nominators to join pools. This is mainly a task for the Wallet/UI development ecosystem, and is beyond the scope of this discussion.</li>
<li>Prevent too many waiting nominators to be created. The reason being that I speculate that most of these nominators have&nbsp;erroneously&nbsp;in the waiting queue, and prefer joining pools instead.</li>
</ul>
To achieve the second goal, we can set the nomination limits (10 DOTs, 50_000) such that the system is not so&nbsp;inviting to waiting nominators. In other words, the system should try and prevent nominators from being created, if they are certainly going to end up being in the waiting queue.
For example, we empirically know that the actual amount of DOTs needed to be an active nominator is around 200 DOTs as of this writing. Therefore, we can set the minimum nomination limit to a higher value such as 100.
Note that keeping a buffer of waiting nominators is a positive factor for Polkadot's economic security. It allows for buffer of waiting nominators to be ready, should a (malicious) cluster of nominators decide to chill all at once, preventing nothing at stake issues. Therefore, I am not suggesting lowering 50_000 as well, and find that a reasonable bound. But, with nomination pools, I do think we should immediately forward anyone with less than e.g. 50 DOTs to join pools instead, and the way to do that is to immediately reject their nominate transaction.
<ul aria-live="polite">
<li tabindex="-1" aria-atomic="true" data-scroll-tokens="$xj3dQq54FAWCyjKPKFdvV4bpYdSZGzCJWh98jeQa1Q4" data-layout="group" data-self="false" data-event-id="$xj3dQq54FAWCyjKPKFdvV4bpYdSZGzCJWh98jeQa1Q4" data-has-reply="false"><a href="../post/1224">https://polkadot.polkassembly.io/post/1224</a>
<div>
<div>&nbsp;</div>
</div>
</li>
</ul>

Schedule the currently externally-proposed majority-carries referendum to be tabled
immediately. If there is no externally-proposed referendum currently, or if there is one
but it is not a majority-carries referendum then it fails.

The dispatch of this call must be `FastTrackOrigin`.

- `proposal_hash`: The hash of the current external proposal.
- `voting_period`: The period that is allowed for voting on this proposal.
	Must be always greater than zero.
	For `FastTrackOrigin` must be equal or greater than `FastTrackVotingPeriod`.
- `delay`: The number of block after voting has ended in approval and this should be
  enacted. This doesn't have a minimum amount.

Emits `Started`.

Weight: `O(1)`

Update the various staking configurations .

* `min_nominator_bond`: The minimum active bond needed to be a nominator.
* `min_validator_bond`: The minimum active bond needed to be a validator.
* `max_nominator_count`: The max number of users who can be a nominator at once. When
  set to `None`, no limit is enforced.
* `max_validator_count`: The max number of users who can be a validator at once. When
  set to `None`, no limit is enforced.
* `chill_threshold`: The ratio of `max_nominator_count` or `max_validator_count` which
  should be filled in order for the `chill_other` transaction to work.
* `min_commission`: The minimum amount of commission that each validators must maintain.
  This is checked only upon calling `validate`. Existing validators are not affected.

RuntimeOrigin must be Root to call this function.

NOTE: Existing nominators and validators will not be affected by this update.
to kick people under the new limits, `chill_other` should be called.

: 
1. Recap on current staking system - open nomination market with a minimum of 10 DOTs and a maximum of 50_000 nominators chosen to participate in election process. 
2. Introduction of nomination pools to simplify process.
3. Cluster nominators into active and waiting categories.
4. Encourage waiting nominators to join pools.
5. Set nomination limits to a higher value than 10 DOTs, such as 100 to prevent too many waiting nominators to be created.
6. Keeping a buffer of waiting nominators is good for economic security.

#65 Proposal: Slightly higher nomination limits

No Active Proposals