feat: 🔧 prevent jailing high stake validators #963
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ToasterTheBrave
approved these changes
Aug 31, 2023
byte-bandit
force-pushed
the
feature/708-consensus-power-aware-jailing
branch
from
0f9ae72
to
f64893a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Github tickets
Background
The only security measurement in place during jailing so far was a check to see that Paloma would not run with less than 1 validator.
This change adds a new safeguard, making sure that a validator will not be jailed if they're holding 25% or more of the entire network stake.
Testing completed
Breaking changes