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

Precision fix 2026-08-19: the three-seal anchor minimum has been enforced since 2026-08-14 (the schedule step is at block 13,034,000 but an emergency ceiling held the effective minimum to one until then); anchors universal since block 13,889,296

Browse Source
This commit is contained in:
Aere Network 2026-08-19 15:46:53 +03:00
parent b7669355eb
commit ac7c0adaa5
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -15,7 +15,7 @@ live chain without asking you to trust anything here.
consensus post-quantum, and nothing in the precompile patches touches consensus.**
Consensus on chain 2800 is **hybrid post-quantum in a precise and limited sense**, by a separate
mechanism: the QBFT header anchor in `anchor/` and `patches/0003`. Since block 13,034,000 every
mechanism: the QBFT header anchor in `anchor/` and `patches/0003`. Since 2026-08-14 every
32nd block (an anchor block) must carry, under its block hash, a certificate of at least three
valid Falcon-512 validator seals (f+1 of nine; eight or nine are carried in practice), and a node
does not finalize an anchor block without it. Classical secp256k1 ECDSA QBFT still finalizes every

2
RUN-A-NODE.md
View File

@ -61,7 +61,7 @@ running a configuration the chain does not.
Since block 13,014,000 every 32nd header of chain 2800 carries a sixth element in its QBFT
`extraData`: a certificate of validator Falcon-512 seals, universal since block 13,889,296 and
enforced at a minimum of three seals per anchor block (f+1 of nine) since block 13,034,000. A node
enforced at a minimum of three seals per anchor block (f+1 of nine) since 2026-08-14. A node
rejects an anchor block whose certificate holds fewer than three valid seals. (Correction 2026-08-19:
an earlier version of this paragraph said that from block 14,050,000 the network refuses to finalize
any block without a post-quantum quorum; the per-block rule armed at that height is retired in the

2
anchor/README.md
View File

@ -17,7 +17,7 @@ should not be confused:
1. **The binding.** From block 13,014,000 the block hash of every anchored header (every 32nd
block) commits to a Falcon-512 certificate signed by the validators. That is a binding, not a
replacement: a rewrite of anchored history must also forge the post-quantum signatures.
2. **The enforced minimum.** From block 13,034,000 a node does not finalize an anchor block unless
2. **The enforced minimum.** Since 2026-08-14 a node does not finalize an anchor block unless
its certificate holds at least three valid Falcon-512 seals (f+1 of nine, the guarantee that at
least one honest validator signed; eight or nine are carried in practice). Blocks between
anchors carry no Falcon seals and are finalized by ECDSA alone, so the post-quantum guarantee