Repository navigation
Conversation
The violation rules share a demotion budget, so processing every validator in one address-ordered pass let a minor violator take the last slot ahead of a severe one. Process each rule in passes ordered by what a transition consumes, and order validators by severity within a pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The violation rules share a demotion budget, so processing every validator in one address-ordered pass let a minor violator take the last slot ahead of a severe one. Each rule now runs in passes ordered by what a transition consumes, and validators are ordered by severity within a pass, with addresses breaking the remaining ties.
Implemented in kaiachain/kaia#1050.