From 81562a179aec777d13d19c86f6abdc09c9c2c017 Mon Sep 17 00:00:00 2001 From: alex <68071075+a-jwc@users.noreply.github.com> Date: Fri, 13 Aug 2021 08:05:14 -0700 Subject: [PATCH] Resolves #1554 (#2456) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Update learn-scams.md (#2440) * update current contributors (#2444) * update current contributors * update current contributors * update current contributors * delete docs/contributors.md * update with new min nomination bond info * spelling error * edit spelling errors and highlighting Co-authored-by: Aleixo Sánchez <15819210+alxs@users.noreply.github.com> Co-authored-by: ajc_ <68071075+yungskum@users.noreply.github.com> --- docs/learn-staking.md | 12 ++++++++++++ docs/maintain-guides-how-to-nominate-polkadot.md | 2 +- 2 files changed, 13 insertions(+), 1 deletion(-) diff --git a/docs/learn-staking.md b/docs/learn-staking.md index 9ed8144bf025..4f5de24b20de 100644 --- a/docs/learn-staking.md +++ b/docs/learn-staking.md @@ -502,6 +502,18 @@ strain of the network due to peer-to-peer message passing. The estimate of the n that Polkadot will have at maturity is around 1000. Kusama, Polkadot's canary network, currently has 900 validator slots in the active set. +## Motion #103: New Minimum Nomination Bond + +At the time of writing (#6,339,031), Polkadot has a maximum nominator count of 22,500, and the current staking configuration prevents new nominators from joining. Motion #103 proposes new nomination limits to the Polkadot network, offering a temporary solution to increase the stability and security of the network. Note that this motion **does not** increase the maximum nominator count. + +The goal of this motion is to increase the minimum nomination bond, allowing new nominators that meet this requirement to particpate in the network's security. This motion will update the value of the minimum nominator bond from 40 DOTs to 80 DOTs and set a new parameter named `chill-threshold`. With `chill-threshold`, the permissionless `chill_other` may only be executed if, and only if, the current nominator count is greater than 90% of the maximum number of nominators. Any existing nominator can update their nomination preferences (amount of DOT bonded, number of nominators, etc.) to adjust to this change. A more permanent solution is in progress. + +**Parameters changed:** +minimum nominator bond : `40` -> `80` + +**Parameters added:** +chill-threshold: `90%` + ## Resources - [How Nominated Proof of Stake will work in Polkadot](https://medium.com/web3foundation/how-nominated-proof-of-stake-will-work-in-polkadot-377d70c6bd43) - diff --git a/docs/maintain-guides-how-to-nominate-polkadot.md b/docs/maintain-guides-how-to-nominate-polkadot.md index ff6a8febffe3..dd941cbf0610 100644 --- a/docs/maintain-guides-how-to-nominate-polkadot.md +++ b/docs/maintain-guides-how-to-nominate-polkadot.md @@ -19,7 +19,7 @@ and finality mechanisms, nominators take a slightly more passive role. Being a n require running a node of your own or worrying about online uptime. However, a good nominator performs due diligence on the validators that they elect. When looking for validators to nominate, a nominator should pay attention to their own reward percentage for nominating a specific validator - -as well as the risk that they bare of being slashed if the validator gets slashed. +as well as the risk that they bear of being slashed if the validator gets slashed. ## Setting up Stash and Controller keys