-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
fix: Count all MNs when calculating voting threshold #5584
base: develop
Are you sure you want to change the base?
Conversation
Co-authored-by: Konstantin Akimov <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK. This solution seems more straightforward.
Minor suggestion
Co-authored-by: Odysseas Gabrielides <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NACK we should not be changing the threshold in such a way that requires 40+ more votes for stuff to pass.
This pull request has conflicts, please rebase. |
Issue being fixed or feature implemented
This is an alternative to #5583
What was done?
Adjust threshold calculations (instead of ignoring votes form invalid MNs)
How Has This Been Tested?
Breaking Changes
Proposals will need 441 absolute YES votes (vs 374 now). A couple of currently passing proposals won't pass in this version (unless they get more YES votes).
Checklist: