From 86e2b34be18d9db49f00470d3c1ce1e18e053b55 Mon Sep 17 00:00:00 2001 From: Aere Network Date: Thu, 5 Nov 2026 04:11:17 +0200 Subject: [PATCH] AIP-22 erratum 2026-11-05: the round in a proposal's header must be the round of its message from H_fin (found 2026-11-02, refused by both clients' validators on chain 2800 since 2026-11-04) --- aips/AIP-22.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/aips/AIP-22.md b/aips/AIP-22.md index fe9610f..3647128 100644 --- a/aips/AIP-22.md +++ b/aips/AIP-22.md @@ -442,6 +442,8 @@ Two refinements to the text above, recorded rather than silently applied: the Me - 2026-11-04, the notes of 2026-10-25 and 2026-10-30 at the top of this document and point 4 of the Motivation: a dated note says that their statement on vote attribution from stage 4 had one exception on the second client until 2026-10-31 12:27Z, as the correction of 2026-11-01 to rule 3 of section 4 says. +- 2026-11-05, section 4 (authorship from verified seals from `H_fin`): the rules did not require the round written in a proposal's header to be the round of its message. From `H_fin` the author of a commit is the id that its ECDSA commit seal resolves to when recovered over the proposal's digest, while the seal is computed over the block given the message round; for a proposal whose header names another round, prepares (over the same digest) are valid and no commit has an author, so the honest validators stay prepared on it and every re-proposal of the prepared value is refused. Reproduced on 2026-11-02 on a rehearsal network of four primary-client validators: one proposer, at its own turn, held the chain until the prepared validators were restarted. Below `H_fin` such a block is given the message round at sealing and commits. Not observed on chain 2800. Rule added, from `H_fin`, or from `H_hdr` where that comes first: before any Prepare, a validator refuses a proposal whose block, given the message round in its header, changes its digest, and refuses a block that cannot be given that round. The second client already refused such a proposal by its own round rule (measured on 2026-11-03 on a rehearsal network with both clients); the primary client applies the rule on chain 2800 since 2026-11-04 (patch 0011 of the public node package). + ## Post-Acceptance Outcome Record Not accepted; nothing to record.