From 934db41c1a0f7a14ed649825cdfba8d95126fe4b Mon Sep 17 00:00:00 2001 From: Sunny Aggarwal Date: Sun, 2 May 2021 16:56:53 -0400 Subject: [PATCH 1/3] CIP3 --- CIPS/cip-3.md | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 CIPS/cip-3.md diff --git a/CIPS/cip-3.md b/CIPS/cip-3.md new file mode 100644 index 0000000..7dd41ca --- /dev/null +++ b/CIPS/cip-3.md @@ -0,0 +1,28 @@ +--- +cip: 3 +title: Minimum Commission Rate Param +status: Draft +type: Core +author: Sunny Aggarwal (@sunnya97) +created: 2021-05-02 +--- + + +# Minimum Commission Rate Param + +## Motivation + +In the cosmos-sdk's staking module, validators are allowed to set their commission rate, that gets charged on all rewards accrued to their delegations. Currently, a validator can set this to any value between 0% and 100%. + +It has been seen in practice that this often leads to validators undercutting each other to provide the lowest commission rate to attract delegators, creating a "race to 0" on commission rates. This leads operating validators to be an unprofitable enterprise for many validators, which had a potentially negative impact on the security of the network. + +## Goals + +Create a new staking module parameter called MinCommissionRate, which sets the lower bound on a commission rate that a validator is allowed to charge. For example, if the MinCommissionRate is set at 10%, this means that a validator can only set their commission rate to a value between 10% and 100%. + +This feature is meant to be fully backwards-compatible as its usage should be optional to chains. Chains opting out of this feature may just keep their MinCommissionRate param at 0%. + + +## Open Questions + +1. If the minimum commission rate param is increased by governance, what should be done for the validator's whose existing commission rate is lower than the new minimum? Should they all be automatically increased to the new minimum? Or should they be grandfathered in at the old commission rate? From 2418c7b18577ea2370d497c35f852bfaeeb92086 Mon Sep 17 00:00:00 2001 From: Sunny Aggarwal Date: Sun, 2 May 2021 16:58:09 -0400 Subject: [PATCH 2/3] fix github handle brackets --- CIPS/cip-3.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CIPS/cip-3.md b/CIPS/cip-3.md index 7dd41ca..2a49807 100644 --- a/CIPS/cip-3.md +++ b/CIPS/cip-3.md @@ -3,7 +3,7 @@ cip: 3 title: Minimum Commission Rate Param status: Draft type: Core -author: Sunny Aggarwal (@sunnya97) +author: Sunny Aggarwal <@sunnya97> created: 2021-05-02 --- From 7b4eb2bd87fb1226fe35237763db145ff657fce9 Mon Sep 17 00:00:00 2001 From: Sunny Aggarwal Date: Sun, 2 May 2021 20:53:19 -0400 Subject: [PATCH 3/3] Update CIPS/cip-3.md Co-authored-by: Dev Ojha --- CIPS/cip-3.md | 1 + 1 file changed, 1 insertion(+) diff --git a/CIPS/cip-3.md b/CIPS/cip-3.md index 2a49807..c657455 100644 --- a/CIPS/cip-3.md +++ b/CIPS/cip-3.md @@ -15,6 +15,7 @@ created: 2021-05-02 In the cosmos-sdk's staking module, validators are allowed to set their commission rate, that gets charged on all rewards accrued to their delegations. Currently, a validator can set this to any value between 0% and 100%. It has been seen in practice that this often leads to validators undercutting each other to provide the lowest commission rate to attract delegators, creating a "race to 0" on commission rates. This leads operating validators to be an unprofitable enterprise for many validators, which had a potentially negative impact on the security of the network. +Cosmos hub governance in the past has overwhelmingly also indicated that it finds 0% commission rates harmful to the success of the network. See cosmos hub proposal 12 (https://www.mintscan.io/cosmos/proposals/12) ## Goals