AIP-22 T5 pe 2800 (H_hdr 25.080.000, 2026-10-30): proza scrisa de proza-trepte.py T5 --scrie --formulare 1

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

README.md

@@ -1,5 +1,7 @@
 # Aere Quantum Migration Toolkit
 
+> **Note added 2026-10-30 (consensus).** Since block 25,080,000 (AIP-22 stage 5) headers no longer carry ECDSA commit seals: each carries the Falcon-512 seal of its proposer instead, and a commit still carries the ECDSA commit seal of its validator as an additional check. Where the note of 2026-09-24 below describes the headers, it describes chain 2800 below that block.
+
 > **Note added 2026-09-24 (consensus).** Where this document says that consensus is classical secp256k1 ECDSA and not post-quantum, read it as the per-block finality statement it was until block 24,300,000 (AIP-22 stage 4, 2026-10-25). Since that block every validator attributes a consensus vote only through its verified post-quantum seal, and a block is post-quantum final once the next anchor, at most 32 blocks later, carries the certificate that covers it; headers still carry classical ECDSA commit seals until AIP-22 stage 5 (this sentence corrected on 2026-10-25). It no longer describes all of consensus on chain 2800: since 2026-08-14 every anchor block must carry a certificate of validator post-quantum seals under its hash (Falcon-512, with SLH-DSA as well since 2026-09-04), and since 2026-09-05 (block 17,250,000) the nine AERE-client validators (nine of the ten) refuse a commit message without a valid Falcon-512 seal of its author, and since 2026-09-08 (block 17,700,000) any QBFT consensus message without one, while the tenth, the second client, enforced that seal only on commit messages until block 24,300,000 and attributes every consensus message only through it since (this clause corrected on 2026-10-12, 2026-10-25 and 2026-10-28; until 2026-10-28 it dated the refusal of every message type to 2026-09-05, the date of the commit layer alone). (Note applied to this document on 2026-10-28.)
 
 A starting toolkit to assess and migrate EVM accounts toward post-quantum
@@ -36,8 +38,7 @@ Node built-ins, Node 18+):
 ## The scope boundary (this never moves)
 
 Migrating an account's authentication to a post-quantum scheme changes how that
-account authorizes. It does NOT make Aere consensus post-quantum. Mainnet 2800
-still seals blocks with classical secp256k1 QBFT, and the on-chain ZK verifiers
+account authorizes. It does NOT make Aere consensus post-quantum. Mainnet 2800 sealed block headers with classical secp256k1 QBFT commit seals until block 25,080,000; since then (AIP-22 stage 5) headers no longer carry ECDSA commit seals and each carries the Falcon-512 seal of its proposer, while a commit still carries the ECDSA commit seal of its validator as an additional check, and the on-chain ZK verifiers
 (BN254 Groth16) are classical. Nothing in this toolkit claims otherwise, and the
 scanner and simulator both restate the boundary in their output.
 

aere-pqc.js

@@ -66,7 +66,7 @@ Global
 
 Scope: this classifies and CONSTRUCTS/SIMULATES migration of ACCOUNT/APPLICATION
 quantum exposure. It never signs, deploys, or moves funds, and it does NOT make
-Aere consensus post-quantum (2800 seals with classical secp256k1 QBFT).`);
+Aere consensus post-quantum (2800: since block 25,080,000 headers no longer carry ECDSA commit seals and each carries the Falcon-512 seal of its proposer; a commit still carries an ECDSA commit seal).`);
   process.exit(code);
 }
 

lib/migrate.js

@@ -182,7 +182,7 @@ export function buildMigrationPlan({ mode = 'pqc', falconPubKey, ecdsaSigner, sa
   validateFalconPubKey(falconPubKey);
   const steps = [];
   const caveats = [
-    'SCOPE: this migrates ACCOUNT AUTHENTICATION to a post-quantum scheme. It does NOT make Aere consensus post-quantum; mainnet 2800 still seals blocks with classical secp256k1 QBFT.',
+    'SCOPE: this migrates ACCOUNT AUTHENTICATION to a post-quantum scheme. It does NOT make Aere consensus post-quantum; mainnet 2800 sealed block headers with classical secp256k1 QBFT commit seals until block 25,080,000; since then (AIP-22 stage 5) headers no longer carry ECDSA commit seals and each carries the Falcon-512 seal of its proposer, while a commit still carries the ECDSA commit seal of its validator as an additional check.',
     'The deployed AerePQCAccount / AereHybridAuth verify Falcon via the SOLIDITY AereFalcon512Verifier (0x4E8e...D8fFC), so one authorization costs ~10.5M gas today (measured 10,278,313 in the live userOp receipt), under the EIP-7825 2^24 per-tx cap. A native SHAKE precompile would cut this sharply (separate roadmap item).',
   ];
 

lib/migrator.js

@@ -326,7 +326,7 @@ export function buildMigrationTransactions({
     transactions,
     warnings,
     signed: false,
-    scope: 'This migrates ACCOUNT AUTHENTICATION to a post-quantum (Falcon-512) key. It does NOT make Aere consensus post-quantum; mainnet 2800 still seals blocks with classical secp256k1 QBFT. These are UNSIGNED transactions; nothing here signs, deploys, or moves funds.',
+    scope: 'This migrates ACCOUNT AUTHENTICATION to a post-quantum (Falcon-512) key. It does NOT make Aere consensus post-quantum; mainnet 2800 sealed block headers with classical secp256k1 QBFT commit seals until block 25,080,000; since then (AIP-22 stage 5) headers no longer carry ECDSA commit seals and each carries the Falcon-512 seal of its proposer, while a commit still carries the ECDSA commit seal of its validator as an additional check. These are UNSIGNED transactions; nothing here signs, deploys, or moves funds.',
   };
 }
 

lib/precompiles.js

@@ -4,8 +4,10 @@
 //
 // SCOPE BOUNDARY (never moves): these are signature/hash verification
 // precompiles on the EVM/account path. NONE of them make Aere consensus
-// post-quantum. Aere mainnet (chain 2800) seals blocks with classical
-// secp256k1 QBFT. Migrating account authentication to a PQC scheme changes how
+// post-quantum. Aere mainnet (chain 2800) sealed block headers with classical
+// secp256k1 QBFT commit seals until block 25,080,000; since then (AIP-22 stage 5)
+// headers no longer carry ECDSA commit seals and each carries the Falcon-512
+// seal of its proposer, while a commit still carries an ECDSA commit seal. Migrating account authentication to a PQC scheme changes how
 // an account authorizes, not how the chain reaches consensus.
 
 // ── Classical, quantum-vulnerable primitives ─────────────────────────────────

lib/readiness.js

@@ -152,7 +152,7 @@ export function buildReadinessReport({
       oneTimeAere: gasToAere(oneTimeGas, gwei),
       ongoingAuthAere: gasToAere(ongoingAuthGas, gwei),
     },
-    scope: 'ACCOUNT/APPLICATION quantum-readiness. This does not, and cannot, make Aere consensus post-quantum (chain 2800 seals with classical secp256k1 QBFT). BN254 ZK verifiers remain classical.',
+    scope: 'ACCOUNT/APPLICATION quantum-readiness. This does not, and cannot, make Aere consensus post-quantum (chain 2800: since block 25,080,000 headers no longer carry ECDSA commit seals and each carries the Falcon-512 seal of its proposer; a commit still carries an ECDSA commit seal). BN254 ZK verifiers remain classical.',
   };
 }
 

scan.js

@@ -37,7 +37,7 @@ Readiness
   GREEN   PQC-capable (uses Aere's live native PQC precompiles 0x0AE1..0x0AE5)
 
 Scope: this classifies ACCOUNT / APPLICATION quantum exposure. It does not, and
-cannot, make Aere consensus post-quantum (chain 2800 seals with secp256k1 QBFT).`);
+cannot, make Aere consensus post-quantum (chain 2800: since block 25,080,000 headers no longer carry ECDSA commit seals and each carries the Falcon-512 seal of its proposer; a commit still carries an ECDSA commit seal).`);
   process.exit(code);
 }