AIP-22 stage R and stage 4 in force on chain 2800 (2026-10-24, 2026-10-25): dated corrections to the README, pq-stark README and AIP index (votes attributed only through verified post-quantum seals since block 24,300,000; headers still admitted on ECDSA commit seals until stage 5), AIP-1 and CONTRIBUTING editorial rules corrected with their date, AIP-22 dated correction to rule 2 of section 4, AIP-3 interval dated
This commit is contained in:
1 parent
4c4d57cd2c
commit
0bf80e42fe
6 files changed
+31
-15
No files matched your search
+13
-5
@@ -235,9 +235,15 @@ correctly formed is not the same person deciding whether the idea wins.*
|
||||
- Every number carries its provenance: **measured**, **spec**, or **estimate**.
|
||||
- Design ceilings (a theoretical maximum throughput) are never presented as
|
||||
measured throughput.
|
||||
- Aere consensus is classical secp256k1 ECDSA QBFT. No AIP claims or implies
|
||||
post-quantum consensus. Post-quantum applies to signatures, accounts and
|
||||
applications only.
|
||||
- Aere consensus is QBFT on chain 2800: anchor blocks carry a post-quantum
|
||||
certificate under their hash since block 13,014,000, and since block
|
||||
24,300,000 (AIP-22 stage 4) a consensus vote counts only with the verified
|
||||
post-quantum seal of its author (headers still carry ECDSA commit seals until
|
||||
AIP-22 stage 5). No AIP claims or implies post-quantum consensus without the
|
||||
limits it states. Post-quantum also applies to signatures, accounts and
|
||||
applications (this rule corrected on 2026-10-26: until that date it said that
|
||||
Aere consensus is classical secp256k1 ECDSA QBFT and that post-quantum applies
|
||||
to signatures, accounts and applications only).
|
||||
|
||||
### 10. Where AIPs live
|
||||
|
||||
@@ -282,8 +288,10 @@ AIP carries the label **"Foundation-ratified (pre-decentralization)"** so that n
|
||||
reader mistakes editorial ratification for trustless governance.
|
||||
|
||||
The intended migration, each step its own Meta AIP: (1) open the validator set
|
||||
beyond the current seven Foundation-operated validators and run a second client
|
||||
as a live producer; (2) introduce a public review period the Foundation cannot
|
||||
beyond the Foundation-operated validators and run a second client as a live
|
||||
producer (seven validators when this was written; ten since 2026-09-11, the
|
||||
tenth running the second client, which produces blocks; this clause corrected
|
||||
on 2026-10-26); (2) introduce a public review period the Foundation cannot
|
||||
unilaterally shorten; (3) move ratification to stake-weighted or
|
||||
validator-weighted approval once an independent staker and validator base exists.
|
||||
|
||||
|
||||
Reference in new issue
Block a user