kip-286: keep an active validator across the epoch transition - #131
Open
hyunsooda wants to merge 1 commit into
Open
kip-286: keep an active validator across the epoch transition#131hyunsooda wants to merge 1 commit into
hyunsooda wants to merge 1 commit into
Conversation
MinActiveCount states the minimum ValActive count required for BFT liveness, but the epoch demotions are unconditional, so a boundary where no entity clears MinStake leaves an empty active set with no in-band recovery. The entities that entered the epoch as ValActive are now retained when the demotions would leave none. Constraint: only the previously active set is retained, so a ValReady or ValPaused entity is never promoted as a side effect Directive: the floor keys on the resulting ValActive count, not on an empty competitor pool - a ValPaused entity in the top 50 stays paused and yields no active validator Confidence: high Scope-risk: narrow Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ian0371
approved these changes
Aug 7, 2026
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
2 participants
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.
Proposed changes
MinActiveCountstates the minimumValActivecount required for BFT liveness, but the epoch demotions are unconditional, so a boundary where no entity clearsMinStakeleaves an empty active set. The entities that entered the epoch asValActiveare now retained when the demotions would leave none.Types of changes
Checklist
I have read the CLA Document and I hereby sign the CLAin first time contributionRelated issues
kaiachain/kaia#1015 implements this.
Further comments
Only the previously active set is retained, so a
ValReadyorValPausedentity is never promoted as a side effect. The floor keys on the resultingValActivecount rather than an empty competitor pool: aValPausedentity in the top 50 stays paused and yields no active validator.