[2dvorak]

Proposed changes

• KIP-227: header.VRank carries ParentRound and ParentCommittedSeal with the decoding rule and parent committee, absent before FORK_BLOCK; signature preimages, BLS key source and header field position; MAX_ROUND as a protocol constant with one-byte rounds, no candidate evaluation above it, invalid messages discarded; cfReport written by the block author for its own most recent proposal, delivery best effort; Example 1 rewritten; the downtime requirement marked as future work.
• KIP-286: committed seals sign keccak256(blockHash || 0x02 || round); the block author must be a member of qualified(N); ceil(2n/3) seal quorum and single-mode header votes; Rule 2 acts on the pfReport that records the failure; the liveness floor and Rule 1 order; suspension as an address-keyed overlay; deadlines carried across states; the ranking stake and the two MinStake roles; the paused-time limit marked as future work; the CandTesting-below-MinStake row, maxSlotAvailable as the one value of both slot limits, the cap applying at the next epoch transition, kaia_getNodesByState in the sets note; reward eligibility follows the node states for block N, including its system transitions, while stake amounts and addresses remain sourced from N-1; under WeightedRandom, header.Rewardbase must match the block author's AddressBookV2 reward address, including on promotion blocks.

Types of changes

Please put an x in the boxes related to your change.

• Bugfix
• KIP Proposal
• KIP Improvement

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• Used the suggested template: https://github.com/kaiachain/KIPs/blob/main/kip-template.md
• I have read the CLA and signed by comment I have read the CLA Document and I hereby sign the CLA in first time contribution
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

Related issues

• Reward eligibility and Rewardbase rules follow kaiax/reward: follow the committee's node states for reward eligibility kaia#1120 (open).

Further comments

[ian0371]

As written, parent.timestamp >= validator.idle_deadline (and the equivalent pause check) expires a validator whose deadline is zero. AddressBookV2 treats timeoutAt == 0 as ‘no timeout’ (_revertIfTimeoutExpired checks timeoutAt != 0), and KIP-290 documents the same meaning. This also matches #1100, which makes zero deadlines persist without expiring.

Please specify that zero deadlines are skipped, for example: if deadline != 0 and parent.timestamp >= deadline. Apply this to both idle and pause deadlines, and clarify that the corresponding user-action checks also skip zero deadlines.

[2dvorak]

Thanks. PTAL 94ea322