This is a short term upgrade proposed to increase the limit of DOTs for nomination from 120 DOTs to 160, maintaining the increase of 40 DOTs that the network has had throughout this period of updating the nominator limit through governance. The reason for this is the combination of the following:

- Polkadot’s [0.9.16](https://github.com/paritytech/polkadot/releases/tag/v0.9.16) upgrade was scheduled to contain a fix that would completely remove the 120 DOTs limit. This explained thoroughly in the monthly staking report of [January 2022](https://gist.github.com/kianenigma/aa835946455b9a3f167821b9d05ba376#january-2022). After the 0.9.16 update, the nomination limit would move to a dynamic system based on demand, rather than a fixed entry barrier.  
- Due to some unforeseen issues arisen after the deployment of 0.9.16 in Kusama, 0/9.16  has not yet been proposed to Polkadot.
- In the meantime, the number of nominators in Polkadot has been increased to reach the 22500 limit. 

As a consequence, we propose to temporarily increase the nomination limit to **160** DOTs. This allows for the permissionless `chill_other` transaction to be used and prune the number of nominators, in order to keep the nomination ecosystem of Polkadot active, whilst we wait for the enactment of runtime 0.9.16 on Polkadot.

 Proposal details: All values are unchanged except for `minNominatorBond`.

![](https://i.ibb.co/vz2vcdj/Screenshot-2022-02-21-at-18-31-17.png)

- Call hash: `0xb2286cbfdd18c265572d3305754b0dbe8ba1fd8da40ef48ff0d5ef40912f2291`

- Call data: `0x0717a00000000000000000000000000000000000000000000000000000000000000001e457000001b0040000015a`

Preimage is submitted. 

- Problem Statement: The Polkadot Runtime needs to be upgraded to v9150, but there are potential issues with the upgrade due to a lack of a corresponding Polkadot companion change for #10043. The intended audience is Polkadot users and developers.
- Significance: The upgrade is crucial for the next runtime and to fix the locked deposit of council voters and the Nicks pallet. However, the potential issues could cause errors in the logs of Kusama nodes.
- Proposed Solution: It is recommended to vote 'Nay' on Referendum 49 until the issue is resolved. An additional runtime upgrade will likely be proposed for Kusama to revert the issue.
- Expected Outcomes: The resolution of the issue will prevent potential errors and risks on the mainnet. The successful upgrade will prepare the system for the next runtime and fix existing issues.

#51 Polkadot’s Update to 160 DOTs as minimum nomination limit: The Reason

No Active Proposals