aere-network/aere-research
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

AIP-22: the measured shape of chain 2800 'today' (Motivation) gave the certificate grid and threshold of before stages 1 and 2; corrected in place with today's values (Falcon-512 every 32nd block, hybrid every 128th, at least seven per scheme) and a dated note (2026-10-12)

Browse Source
This commit is contained in:
Aere Network 2026-10-12 13:16:19 +03:00
parent 994eaacf8e
commit 7a5340aea5
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
aips/AIP-22.md
View File

@ -41,7 +41,7 @@ This AIP makes the finality of every block of an Aere QBFT chain a post-quantum
## Motivation
Chain 2800 today has the following measured shape (sources in the Specification): every validator refuses a commit unless it carries a valid Falcon-512 seal bound to its author, and the nine validators that run the primary client refuse every QBFT message on the hot path (proposal, prepare, commit, round-change) without one, since block 17,700,000; the second client, which runs the tenth validator, refuses any commit without one since block 18,131,633, while its proposal, prepare and round-change layers take effect at stage 4 below (`H_fin`, whose height is not yet set on chain 2800); every 128th block carries a hybrid Falcon-512 + SLH-DSA-SHA2-128s certificate over its parent under the block hash, with at least six valid seals per scheme of the ten validators; and `aere_getPqFinality` returns, on every validator, the Falcon seals it heard for a recent block, re-verified (ten of ten on 2026-09-22). A validator that is online therefore finalizes nothing without post-quantum seals. (Corrected 2026-10-09: until that date this paragraph said that the four message types are refused without a seal "since block 17,700,000 on both clients"; on chain 2800 the second client enforces its commit layer only, and its other three layers take effect at stage 4. See the Errata entry of that date.)
Chain 2800 today has the following measured shape (sources in the Specification): every validator refuses a commit unless it carries a valid Falcon-512 seal bound to its author, and the nine validators that run the primary client refuse every QBFT message on the hot path (proposal, prepare, commit, round-change) without one, since block 17,700,000; the second client, which runs the tenth validator, refuses any commit without one since block 18,131,633, while its proposal, prepare and round-change layers take effect at stage 4 below (`H_fin`, whose height is not yet set on chain 2800); every 32nd block carries a Falcon-512 certificate over its parent under the block hash and every 128th block a hybrid Falcon-512 + SLH-DSA-SHA2-128s one, with at least seven valid seals per scheme of the ten validators (stages 1 and 2 below, active from blocks 20,715,632 and 20,746,736; before them every 128th block, with at least six); and `aere_getPqFinality` returns, on every validator, the Falcon seals it heard for a recent block, re-verified (ten of ten on 2026-09-22). A validator that is online therefore finalizes nothing without post-quantum seals. (Corrected 2026-10-09: until that date this paragraph said that the four message types are refused without a seal "since block 17,700,000 on both clients"; on chain 2800 the second client enforces its commit layer only, and its other three layers take effect at stage 4. See the Errata entry of that date.) (Corrected 2026-10-12: the 2026-10-09 version of this paragraph gave, as today's, the certificate grid and threshold of before stages 1 and 2.)
What remains classical is exactly what a node that is NOT online, one that syncs the history, is asked to believe: