From 54d509e7b8f70bb655d2b0f70add4b9d0400d321 Mon Sep 17 00:00:00 2001 From: Aere Network Date: Wed, 19 Aug 2026 14:37:04 +0300 Subject: [PATCH] Dated note on 20 documents: the post-quantum anchor checkpoint (>=3 of 9 Falcon seals every 32nd block since 13,034,000) qualifies the 'consensus remains classical' statements; the 14,050,000 per-block quorum claim was withdrawn on 2026-08-19 --- AERE-ARCHITECTURE-MAP.md | 2 ++ AERE-BUILD-LOOP-SUMMARY-2026-07-19.md | 2 ++ AERE-CERTORA-FORMAL-VERIFICATION.md | 2 ++ AERE-COMPUTE-MARKET-V3-SUMMARY.md | 2 ++ AERE-COMPUTE-MARKET-V3.md | 2 ++ AERE-CROSS-CLIENT-DETERMINISM.md | 2 ++ AERE-ENGINEERING-SECURITY-SPEC.md | 2 ++ AERE-ERC7683-DESTINATION-SUMMARY.md | 2 ++ AERE-FORMAL-BROADEN-REPORT.md | 2 ++ AERE-POST-QUANTUM-GOVERNANCE.md | 2 ++ AERE-PQ-AGGREGATE-SUMMARY.md | 2 ++ AERE-PQ-SCREEN-SUMMARY.md | 2 ++ AERE-PQ-SCREEN.md | 2 ++ AERE-PROTOCOL-SPECIFICATION.md | 2 ++ AERE-QA-CONSOLIDATION-REPORT.md | 2 ++ AERE-QUANTUM-SAFE-NETWORKING.md | 2 ++ AERE-SHADOW-PRODUCER-SUMMARY.md | 2 ++ AERE-SHADOW-PRODUCER.md | 2 ++ AIP-PQ-TX-2026-07-18.md | 2 ++ DOVADA-PQC-VERIFICABILA-2026-07-20.md | 2 ++ 20 files changed, 40 insertions(+) diff --git a/AERE-ARCHITECTURE-MAP.md b/AERE-ARCHITECTURE-MAP.md index e6730af..a81516e 100644 --- a/AERE-ARCHITECTURE-MAP.md +++ b/AERE-ARCHITECTURE-MAP.md @@ -1,5 +1,7 @@ # Aere Network Architecture Map +> **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 every 32nd block also carries, under its block hash, a certificate of validator Falcon-512 seals, and since block 13,034,000 a node rejects such an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md. + Aere Network is a public, EVM-compatible Layer 1 (chain ID 2800). One diagram replaces pages of prose here: the architecture is best read as a layered stack (Consensus at the bottom, then Execution, Accounts, and Applications on top) with a set of cross-cutting concerns (post-quantum cryptography, zero-knowledge verification, and crypto-agility) that traverse every layer rather than sitting in any single one. This is deliberately not one linear top-to-bottom column: the layers stack, and the transversal concerns cut across all of them. The single most important honesty point, stated up front: consensus today is classical ECDSA (secp256k1) QBFT. Only signatures, accounts, and precompiles are post-quantum. There is no post-quantum consensus live on mainnet, and the on-chain zero-knowledge verifiers are classical BN254 (Shor-breakable) today. Everything below is marked LIVE (on mainnet 2800) or "(roadmap)" (built and tested, but not activated on mainnet). diff --git a/AERE-BUILD-LOOP-SUMMARY-2026-07-19.md b/AERE-BUILD-LOOP-SUMMARY-2026-07-19.md index 22cc940..3e1d4b7 100644 --- a/AERE-BUILD-LOOP-SUMMARY-2026-07-19.md +++ b/AERE-BUILD-LOOP-SUMMARY-2026-07-19.md @@ -1,5 +1,7 @@ # Aere Network: Autonomous Build Loop Summary (2026-07-19) +> **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 every 32nd block also carries, under its block hash, a certificate of validator Falcon-512 seals, and since block 13,034,000 a node rejects such an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md. + A single clean record of the non-stop build loop. Every item below was verified before it was marked done: real numbers where measured, honest `[MEASURE]` / `[VERIFY]` markers where not, and the post-quantum scope boundary kept everywhere (consensus is classical secp256k1 ECDSA QBFT; only signatures, accounts, and precompiles are post-quantum). Nothing here was deployed to mainnet; every activation stays founder-gated. ## Consolidation QA (proof it all coexists) diff --git a/AERE-CERTORA-FORMAL-VERIFICATION.md b/AERE-CERTORA-FORMAL-VERIFICATION.md index 703bf8c..1204bfa 100644 --- a/AERE-CERTORA-FORMAL-VERIFICATION.md +++ b/AERE-CERTORA-FORMAL-VERIFICATION.md @@ -1,5 +1,7 @@ # Spec 21: Certora formal-verification specifications for Aere Network's safety-critical contracts +> **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 every 32nd block also carries, under its block hash, a certificate of validator Falcon-512 seals, and since block 13,034,000 a node rejects such an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md. + Status date: 2026-07-19. Author: Aere Network engineering (self-authored CVL). ## HONEST STATUS BANNER (read first) diff --git a/AERE-COMPUTE-MARKET-V3-SUMMARY.md b/AERE-COMPUTE-MARKET-V3-SUMMARY.md index a139e13..f6f91f7 100644 --- a/AERE-COMPUTE-MARKET-V3-SUMMARY.md +++ b/AERE-COMPUTE-MARKET-V3-SUMMARY.md @@ -1,5 +1,7 @@ # Spec 10: Aere Compute Market V3 (proof-carrying DePIN) +> **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 every 32nd block also carries, under its block hash, a certificate of validator Falcon-512 seals, and since block 13,034,000 a node rejects such an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md. + Revised 2026-07-20. The prior revision of this file described V3 before the liveness review; the sections below supersede it. diff --git a/AERE-COMPUTE-MARKET-V3.md b/AERE-COMPUTE-MARKET-V3.md index 0db1b98..d25e4a8 100644 --- a/AERE-COMPUTE-MARKET-V3.md +++ b/AERE-COMPUTE-MARKET-V3.md @@ -1,5 +1,7 @@ # Aere Compute Market V3 +> **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 every 32nd block also carries, under its block hash, a certificate of validator Falcon-512 seals, and since block 13,034,000 a node rejects such an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md. + Proof-carrying decentralized compute (DePIN) settlement for Aere Network. ## What it is diff --git a/AERE-CROSS-CLIENT-DETERMINISM.md b/AERE-CROSS-CLIENT-DETERMINISM.md index 45eb816..18b3e46 100644 --- a/AERE-CROSS-CLIENT-DETERMINISM.md +++ b/AERE-CROSS-CLIENT-DETERMINISM.md @@ -1,5 +1,7 @@ # Aere Network Cross-Client Determinism +> **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 every 32nd block also carries, under its block hash, a certificate of validator Falcon-512 seals, and since block 13,034,000 a node rejects such an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md. + Technical specification. Chain 2800 (Aere Network mainnet). Grounding and consistency: this document is the reproducible proof behind Aere's diff --git a/AERE-ENGINEERING-SECURITY-SPEC.md b/AERE-ENGINEERING-SECURITY-SPEC.md index 6e19c0f..416c254 100644 --- a/AERE-ENGINEERING-SECURITY-SPEC.md +++ b/AERE-ENGINEERING-SECURITY-SPEC.md @@ -1,5 +1,7 @@ # Aere Network Engineering and Security Specification +> **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 every 32nd block also carries, under its block hash, a certificate of validator Falcon-512 seals, and since block 13,034,000 a node rejects such an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md. + **Status:** Internal draft for adversarial review and for the external audit that follows. Every claim is meant to be checkable against the repository, the live chain (chain ID 2800), or the cited formal-verification artifacts. This document is internally verified and adversarially self-reviewed; it is not yet externally audited. Read every guarantee as "internally verified, not externally attested" until an independent audit completes. A single framing statement governs the entire document and is repeated because it is the most common thing to get wrong about Aere: smart contracts and accounts on Aere can verify post-quantum signatures (Falcon, ML-DSA, SLH-DSA) through live EVM precompiles; consensus remains classical ECDSA / QBFT, and the on-chain zero-knowledge verifiers remain classical BN254 pairing checks. Aere is post-quantum at the signature and precompile layer and classical at the consensus and ZK verification layers. The chain as a whole is not post-quantum, and this document never claims it is. diff --git a/AERE-ERC7683-DESTINATION-SUMMARY.md b/AERE-ERC7683-DESTINATION-SUMMARY.md index 705c3a7..e713845 100644 --- a/AERE-ERC7683-DESTINATION-SUMMARY.md +++ b/AERE-ERC7683-DESTINATION-SUMMARY.md @@ -1,5 +1,7 @@ # Spec 8 - ERC-7683 Destination Settler for Aere Network +> **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 every 32nd block also carries, under its block hash, a certificate of validator Falcon-512 seals, and since block 13,034,000 a node rejects such an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md. + ## What was built (all new files, deployed origin contracts untouched) 1. `aere-contracts/contracts/intents/AereDestinationSettler.sol` diff --git a/AERE-FORMAL-BROADEN-REPORT.md b/AERE-FORMAL-BROADEN-REPORT.md index d635eb8..9a99bff 100644 --- a/AERE-FORMAL-BROADEN-REPORT.md +++ b/AERE-FORMAL-BROADEN-REPORT.md @@ -1,5 +1,7 @@ # Formal-verification broadening: new contract SMT models + canonical runner consolidation +> **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 every 32nd block also carries, under its block hash, a certificate of validator Falcon-512 seals, and since block 13,034,000 a node rejects such an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md. + Date: 2026-07-19. Tooling: Python 3.14.4, z3 4.16.0 (real z3 verdicts, no fabricated greens). All verdicts below were produced by actually running the scripts. diff --git a/AERE-POST-QUANTUM-GOVERNANCE.md b/AERE-POST-QUANTUM-GOVERNANCE.md index e5cd509..3dc0caa 100644 --- a/AERE-POST-QUANTUM-GOVERNANCE.md +++ b/AERE-POST-QUANTUM-GOVERNANCE.md @@ -1,5 +1,7 @@ # Spec 29: Post-Quantum Governance +> **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 every 32nd block also carries, under its block hash, a certificate of validator Falcon-512 seals, and since block 13,034,000 a node rejects such an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md. + Aere Network, chain ID 2800. Design specification. Status: DESIGN plus a capability on already-deployed primitives. Not activated. ## Honest scope, stated first diff --git a/AERE-PQ-AGGREGATE-SUMMARY.md b/AERE-PQ-AGGREGATE-SUMMARY.md index 64bc4a9..4248fa0 100644 --- a/AERE-PQ-AGGREGATE-SUMMARY.md +++ b/AERE-PQ-AGGREGATE-SUMMARY.md @@ -1,5 +1,7 @@ # Spec 6: AerePQAggregate build summary +> **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 every 32nd block also carries, under its block hash, a certificate of validator Falcon-512 seals, and since block 13,034,000 a node rejects such an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md. + ## What was built Constant-cost on-chain verification of a t-of-n POST-QUANTUM committee authorization via ONE succinct SP1 proof, exposed as an ERC-4337 path and a portable ERC-7579 validator module. diff --git a/AERE-PQ-SCREEN-SUMMARY.md b/AERE-PQ-SCREEN-SUMMARY.md index 6b6f1b2..8fe0999 100644 --- a/AERE-PQ-SCREEN-SUMMARY.md +++ b/AERE-PQ-SCREEN-SUMMARY.md @@ -1,5 +1,7 @@ # Spec 7: AerePQ-Screen (post-quantum compliance passport) - SUMMARY +> **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 every 32nd block also carries, under its block hash, a certificate of validator Falcon-512 seals, and since block 13,034,000 a node rejects such an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md. + ## What was built Institution-grade post-quantum compliance passport for Aere Network, built ON the existing compliance stack (AereZKScreen, AereCompliancePool, AereSanctionsRegistry, AerePQCKeyRegistry) without modifying diff --git a/AERE-PQ-SCREEN.md b/AERE-PQ-SCREEN.md index e4268be..53065b5 100644 --- a/AERE-PQ-SCREEN.md +++ b/AERE-PQ-SCREEN.md @@ -1,5 +1,7 @@ # AerePQ-Screen: an institution-grade post-quantum compliance passport +> **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 every 32nd block also carries, under its block hash, a certificate of validator Falcon-512 seals, and since block 13,034,000 a node rejects such an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md. + AerePQ-Screen upgrades Aere Network's compliance stack so it interoperates with the identity standards banks and regulated institutions already use, W3C Verifiable Credentials 2.0, Decentralized Identifiers (DID), and the ERC-3643 / ONCHAINID accreditation model, and adds the differentiator no diff --git a/AERE-PROTOCOL-SPECIFICATION.md b/AERE-PROTOCOL-SPECIFICATION.md index 2fe5234..6f945b3 100644 --- a/AERE-PROTOCOL-SPECIFICATION.md +++ b/AERE-PROTOCOL-SPECIFICATION.md @@ -1,5 +1,7 @@ # Aere Network Protocol Specification +> **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 every 32nd block also carries, under its block hash, a certificate of validator Falcon-512 seals, and since block 13,034,000 a node rejects such an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md. + **Document:** spec-24-protocol-spec **Chain:** Aere Network mainnet, chain ID 2800 (`0xaf0`) **Base execution client:** Hyperledger Besu 26.4.0 line (fork), with a second client (patched Nethermind 1.39.0) as a validation cross-check diff --git a/AERE-QA-CONSOLIDATION-REPORT.md b/AERE-QA-CONSOLIDATION-REPORT.md index 1701ab6..85813ee 100644 --- a/AERE-QA-CONSOLIDATION-REPORT.md +++ b/AERE-QA-CONSOLIDATION-REPORT.md @@ -1,5 +1,7 @@ # Aere Network Consolidation QA Report +> **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 every 32nd block also carries, under its block hash, a certificate of validator Falcon-512 seals, and since block 13,034,000 a node rejects such an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md. + Date: 2026-07-19 Scope: the ~12 new Solidity contracts plus their tests added during the build loop, and a cross-document consistency check over the new AERE-*.md docs. Method: read-and-run audit only. No contract or test was modified. Results below are the real command outputs. diff --git a/AERE-QUANTUM-SAFE-NETWORKING.md b/AERE-QUANTUM-SAFE-NETWORKING.md index a583724..fd7d3b6 100644 --- a/AERE-QUANTUM-SAFE-NETWORKING.md +++ b/AERE-QUANTUM-SAFE-NETWORKING.md @@ -1,5 +1,7 @@ # Aere Network Quantum-Safe Networking (Transport Layer) +> **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 every 32nd block also carries, under its block hash, a certificate of validator Falcon-512 seals, and since block 13,034,000 a node rejects such an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md. + **Spec #30, Wave 1. Design document. Status: NOT LIVE.** > This document specifies making Aere's network **transport** post-quantum. It is a diff --git a/AERE-SHADOW-PRODUCER-SUMMARY.md b/AERE-SHADOW-PRODUCER-SUMMARY.md index 852ede5..5f909ee 100644 --- a/AERE-SHADOW-PRODUCER-SUMMARY.md +++ b/AERE-SHADOW-PRODUCER-SUMMARY.md @@ -1,5 +1,7 @@ # Spec 13: Self-verifying parallel Shadow Block Producer +> **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 every 32nd block also carries, under its block hash, a certificate of validator Falcon-512 seals, and since block 13,034,000 a node rejects such an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md. + Date: 2026-07-19. Chain 2800 (Aere Network mainnet), head ~10,364,611 at build time. ## What was built diff --git a/AERE-SHADOW-PRODUCER.md b/AERE-SHADOW-PRODUCER.md index 10918f2..d3964f5 100644 --- a/AERE-SHADOW-PRODUCER.md +++ b/AERE-SHADOW-PRODUCER.md @@ -1,5 +1,7 @@ # Aere Shadow Block Producer +> **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 every 32nd block also carries, under its block hash, a certificate of validator Falcon-512 seals, and since block 13,034,000 a node rejects such an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md. + Technical specification. Chain 2800 (Aere Network mainnet). Grounding and consistency: this document describes a live compliance monitor that diff --git a/AIP-PQ-TX-2026-07-18.md b/AIP-PQ-TX-2026-07-18.md index 755dfe3..f4727ed 100644 --- a/AIP-PQ-TX-2026-07-18.md +++ b/AIP-PQ-TX-2026-07-18.md @@ -1,5 +1,7 @@ # AIP-8: Post-Quantum-Authorized Transaction Envelope (EIP-2718 Type 0x2A) +> **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 every 32nd block also carries, under its block hash, a certificate of validator Falcon-512 seals, and since block 13,034,000 a node rejects such an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md. + ## Preamble | Field | Value | diff --git a/DOVADA-PQC-VERIFICABILA-2026-07-20.md b/DOVADA-PQC-VERIFICABILA-2026-07-20.md index 7da1ba8..0d81a8e 100644 --- a/DOVADA-PQC-VERIFICABILA-2026-07-20.md +++ b/DOVADA-PQC-VERIFICABILA-2026-07-20.md @@ -1,5 +1,7 @@ # Dovada PQC verificabila. Tested commands and real output +> **Nota adaugata 2026-08-19.** Afirmatiile de aici ca pe lantul 2800 consensul e (sau ramane) clasic ECDSA secp256k1 QBFT au fost scrise inainte de ancora post-cuantica din antet si raman adevarate pentru finalitatea bloc cu bloc. De la blocul 13.014.000 fiecare al 32-lea bloc poarta, sub amprenta lui, un certificat de sigilii Falcon-512 ale validatorilor, iar de la 13.034.000 un nod respinge un astfel de bloc de ancora cu mai putin de 3 sigilii valide (f+1 din 9; 8-9 purtate in practica). E un punct de control post-cuantic la ~16 secunde, nu un cvorum pe fiecare bloc: afirmatia publicata pe 15 august ca de la 14.050.000 niciun bloc nu se finalizeaza fara cvorum post-cuantic era gresita (regula armata atunci e retrasa in codul livrat in favoarea regulilor ancorei) si a fost retrasa pe 19 august. Detalii: https://aere.network/quantum.html si depozitul aere-node, anchor/README.md. + **Date:** 2026-07-20 **Chain:** AERE mainnet, chain ID 2800 (`0xaf0`) **Endpoints used:** `https://rpc.aere.network` and `https://rpc2.aere.network`