-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Validator Min. Commission 5% #109
Comments
This issue reminds me of the millions of people who suffer from the side effects of policies created without deep reflection by the government. It sounds simple, but it requires a lot of research. CosmosSDK does not allow us to query addresses participated in voting for closed proposals which is frustrating. I wish to see how many addresses actually participated in voting and how the voting power is distributed. Terra Classic's token economics are completely broken, so I don't think it's mandatory to implement just because a proposal is passed. |
There could be a misunderstanding in what I wrote above, but my opinion is that in-depth discussions is required, rather than rushing to create and apply solution because the proposal is passed. |
I agree with @inon-man and have always been of the opinion that in the current situation the "Tokenomics of Terra" are broken to the point where we have to assume that governance is owned by the few lucky people who caught the bottom and that we will have to build for a long time to attract enough new investors to dilute that voting power in a meaningful way. This consequently is also why trying to "force redelegation via constraints" is never going to work until we can associate addresses with a DID component ala https://hypersign.id/ or https://identity.foundation/ion/. With that said I think the min commission makes sense for another reason, namely ensuring the validators are actually economically viable to run. As such that is more important to me then trying to enforce decentralization via centralized code changes and arguments about voting power (which is already tightly controlled and a situation best resolved by the market itself if we want a sustainable foundation for the future). The best way to achieve this imho is by incentivize the network and governance to course correct via introducing new features that can incentives "real world utility" that can be taxed and increase the rewards for the network validators to the point where they can more then break even and thus do not have to resort to "veto blocking to collect fees" or "partitioning their validators to circumvent the BFT guard". |
See discussion @ #127 |
Re-opened this item as we should have resourcing to have this completed during Q2, and due to it passing governance. It will be prioritized such that it does not impact the proposed timing of the upgrade to parity. |
waiting for core to update to cosmos - sdk 46, then gov change params for min commission |
Set validator min conmission rateAbstractThis poposal aims to set the minimum commission rate(aka. ImplementationOption 1Add Reference: terra-money/core#47 Option 2If we don't need to change Option 3Fork Option1 vs Option2 vs Option3
MigrationEach option requires a forced increase of the validator's commission to 5%. We can implement it in the next
|
I am good with option 3 |
What is with validators that have set MAX commission rate to < 5% ? |
Me too. |
will be update to 5% |
@alchemist-ti - following @StrathCole's suggestion I would add this logic to upgrade handler
|
❤️ make sense. I updated to |
Proceeded with option 3 as per Alchemist-ti's recommendation. Attempting to include this in the v2.1.0 release -- to be confirmed. |
Problem definition
With the passing of proposal 11322 the community expressed the wish to implement a minimum commission of 5% for validators on the network. This highly relates to #89.
Update: Given that this is feature in Cosmos SDK 0.46, a temporary solution that allows for a minimum 5% commission to be enforced for all validators should be sufficient.
The text was updated successfully, but these errors were encountered: