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

Seals stated as many as the quorum, proving that those validators signed, not that the block was decided (AIP-22 erratum of 2026-10-01)
Some checks failed
contracts-ci / Install (lockfile) → compile → full test suite (push) Has been cancelled
Details
contracts-ci / Ethereum interop (EIP-2537 BLS, prague hardfork) (push) Has been cancelled
Details
contracts-ci / PQC known-answer tests (NIST vectors) (push) Has been cancelled
Details
contracts-ci / Coverage (scoped, with artifacts) (push) Has been cancelled
Details

Browse Source
This commit is contained in:
Aere Network 2026-10-01 19:11:55 +03:00
parent e70554da9c
commit e18c5cdc36
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -21,7 +21,7 @@ checkpoint every 32 blocks.** Since block 13,014,000 anchor blocks carry, under
certificate of validator post-quantum seals (Falcon-512, with SLH-DSA-SHA2-128s as well since
2026-09-04, at every 128th block since 2026-09-29; every anchor was 128 blocks apart from block
17,225,968 to block 20,746,736). Since block 20,715,632 (2026-09-29) a node rejects an anchor block
with fewer than seven valid seals per scheme, the full quorum of the ten validators; the minimum was
with fewer than seven valid seals per scheme, as many as the quorum of the ten validators (the seals prove those validators signed the block, not that it was decided, per the AIP-22 erratum of 2026-10-01); the minimum was
three (f+1 of nine, not a quorum) from 2026-08-14 and six from 2026-08-21. That
checkpoint lives in the aere-node repository (patch 0003 and `anchor/`), not in this one: nothing in
this repository makes consensus post-quantum, and the chain is not "post-quantum consensus" without