aere-network/aere-docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
main
aere-docs/AERE-QA-CONSOLIDATION-REPORT.md
Aere Network e4cead319d Initial public release 
Aere Network public source. Everything here can be checked against the live
chain (chain id 2800, https://rpc.aere.network).

Scope note, stated up front rather than buried: consensus on chain 2800 is
classical secp256k1 ECDSA QBFT. The post-quantum work in this repository is at
the signature, precompile, account and transport layers. Nothing here makes the
consensus post-quantum, and no document in it should be read as claiming so.
2026-07-20 01:01:36 +03:00

8.3 KiB
Raw Permalink Blame History

Aere Network Consolidation QA Report

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.

PART 1: COMPILE THE WHOLE SUITE

Command: cd aerenew/contracts && npx hardhat clean && npx hardhat compile (clean was run first, because a plain compile reported "Nothing to compile" from cache; the numbers below are from a genuine full rebuild.)

VERDICT: GREEN. Compiled 339 Solidity files successfully (evm targets: cancun, paris).

All of the new contracts are present in the tree and compiled with zero errors:

  • contracts/oracle/AereRandomnessBeaconV2.sol
  • contracts/AereRecoveryRegistry.sol
  • contracts/erc8004/ (IERC8004.sol, AereIdentityRegistry8004.sol, AereReputationRegistry8004.sol, AereValidationRegistry8004.sol, AereAP2MandateVerifier.sol)
  • contracts/mpc/AerePQAggregateVerifier.sol
  • contracts/modular/AerePQAggregateModule.sol
  • contracts/compliance/AereTrustRegistry.sol, AereVerifiableCredential.sol, AereBitstringStatusList.sol
  • contracts/intents/AereDestinationSettler.sol
  • contracts/depin/AereComputeMarketV3.sol
  • contracts/agentic/AereVectorStore.sol
  • contracts/pqc/AereAccountMigrator.sol
  • contracts/pqfinality/AerePQAttestationKeyRegistry.sol, AereFinalityCertificateVerifier.sol

Compiler warnings only (no errors), all pre-existing and non-blocking:

  • Transient storage (EIP-1153) advisory notes in AereCancunCanary.sol (reentrancy-guard pattern, benign).
  • Declaration-shadowing notes (constructor param vs same-named getter) in AereGovernanceStaked.sol, agentic/AereAIReputation.sol, agentic/AereAgentBond.sol.
  • Shift-result-type advisory in pqc/AereFalcon1024Verifier.sol, AereFalcon512Verifier.sol, AereMLDSA44Verifier.sol.
  • Unused-parameter notes in zkverify/AereHalo2CubicVerifier.sol.
  • Mutability-can-be-pure note in AereConsensus.sol.

None of these touch the new contracts under audit except cosmetically, and none block compilation.

PART 2: NEW TEST FILES (run one at a time)

Each file run with npx hardhat test test/<file>. AereRandomnessBeaconV2 was run with the prague config as instructed (--config hardhat.config.prague.js); EIP-2537 was present in that EVM, so the real pairing path ran.

# Test file Passing Pending Failing
1 test/AereRecoveryRegistry.test.js 10 0 0
2 test/erc8004-adapters.test.js 18 0 0
3 test/AerePQAggregate.test.js 17 0 0
4 test/aere-pq-screen.test.js 12 0 0
5 test/destination-settler.test.js 4 0 0
6 test/AereRandomnessBeaconV2.test.js (prague config) 15 1 0
7 test/AereComputeMarketV3.test.js 13 0 0
8 test/aere-vector-store.test.js 8 0 0
9 test/account-migrator.test.js 9 0 0
10 test/AerePQFinalityCertificate.test.js 12 0 0
GRAND TOTAL 118 1 0

VERDICT: GREEN. 118 passing, 1 pending, 0 failing across all 10 new test files.

Note on the 1 pending (file 6): it is the deliberately-skipped "without EIP-2537, a genuine sig is also rejected (never stub-true)" fail-closed-absence check. The harness prints "EIP-2537 present: this fail-closed-absence check is not applicable" and marks it pending because the prague EVM DOES have EIP-2537 (real BLS12-381 pairing verification, "YES"). This is expected behavior, not a failure: the positive pairing-verification tests all ran and passed on the real precompile path.

PART 3: CROSS-DOCUMENT CONSISTENCY CHECK

Grepped across the new AERE-*.md docs in aerenew/docs/. Findings against each invariant:

  1. Burn = 37.5% of the validator reward, cap 50%, NOT a base-fee burn. CONSISTENT. Every doc that mentions the burn describes it as a cut of the validator coinbase block reward, burnBps default 3750 (37.5%), hard-capped at MAX_BURN_BPS = 5000 (50%), applied above consensus by AereCoinbaseSplitterV2, explicitly not an EIP-1559 protocol base-fee burn. See AERE-ENGINEERING-SECURITY-SPEC.md:205-217, AERE-PROTOCOL-SPECIFICATION.md:497-540, AERE-EIP-COMPATIBILITY-MATRIX.md:109, AERE-AIP-PROCESS-AND-INDEX.md:110/137, AERE-CERTORA-FORMAL-VERIFICATION.md:170/187-188. No contradiction. (Several docs carry an honest [VERIFY] marker asking that EIP-1559 base-fee DISPOSAL be stated precisely; that is an open verification item, and it is careful to keep disposal distinct from the validator-reward-cut burn, so it does not contradict the invariant.)

  2. Live precompiles 0x0AE1..0x0AE5 (mainnet, block 9,189,161); 0x0AE6/0x0AE7 testnet-only; 0x0AE8 non-working skeleton. CONSISTENT. Uniform across AERE-PROTOCOL-SPECIFICATION.md (4.2-4.8, tables at 480-487, 653-670), AERE-EIP-COMPATIBILITY-MATRIX.md:91-98, AERE-BENCHMARK-REPORT.md:253-264, AERE-ARCHITECTURE-MAP.md:43-44, AERE-NIST-VALIDATION-STATUS.md:28/90, AERE-MIGRATION-TOOLKIT.md:87. 0x0AE1-0x0AE5 are consistently "live on mainnet 2800, activated block 9,189,161"; 0x0AE6 (ML-KEM-768) and 0x0AE7 (Falcon HashToPoint) are consistently "testnet only, founder/audit-gated, not on mainnet"; 0x0AE8 (hash-based STARK verify) is consistently "reference skeleton, non-working, never to be activated as-is." No contradiction. Scope caveat (2026-07-19 finding): 0x0AE8's confirmed generic components verify BabyBear + FRI STARKs (Aere's OWN Plonky3 circuits), NOT SP1 6.1.0, which is Hypercube (KoalaBear multilinear); docs that still label 0x0AE8 "SP1 inner STARK verify" carry the corrected scope. See AERE-STARK-SP1-RECURSION-AIR-PORT-SPEC-SUMMARY.md.

  3. Consensus params N=7, f=2, quorum 5 of 7. CONSISTENT. Stated identically everywhere it appears: AERE-ENGINEERING-SECURITY-SPEC.md:37/138/227 ("N=7 validators, f=2, commit quorum 2f+1 = 5 of 7"), AERE-AIP-PROCESS-AND-INDEX.md:166, AERE-EIP-COMPATIBILITY-MATRIX.md:3, AERE-CROSS-CLIENT-DETERMINISM.md:93/373, AERE-ERC7683-DESTINATION.md:113-114. The live set is consistently N=7. N=9 appears only as a forward-looking target inside the fault matrix (AERE-FAULT-INJECTION-HARNESS.md:57-59) and is clearly labeled a design/target configuration, not the live set. No contradiction.

  4. PQC scope boundary (consensus is classical ECDSA QBFT; only signatures/accounts/precompiles are post-quantum; PQ consensus is NOT live). CONSISTENT and repeatedly reinforced, never contradicted. AERE-ARCHITECTURE-MAP.md:5 leads with it ("consensus today is classical ECDSA (secp256k1) QBFT ... There is no post-quantum consensus live on mainnet"). Echoed in AERE-AIP-PROCESS-AND-INDEX.md:148/277, AERE-CERTORA-FORMAL-VERIFICATION.md:25, AERE-ENGINEERING-SECURITY-SPEC.md:58/313, AERE-ERC8004-SUMMARY.md:53-54, AERE-ERC8004-X402-CONFORMANCE.md:22-23, AERE-ERC7683-DESTINATION.md:179-181, AERE-COMPUTE-MARKET-V3.md:86, AERE-MIGRATION-TOOLKIT.md:74, AERE-PQ-SCREEN-SUMMARY.md:58, AERE-EIP-COMPATIBILITY-MATRIX.md:101, AERE-CROSS-CLIENT-DETERMINISM.md:66/351. The fault-injection harness (AERE-FAULT-INJECTION-HARNESS.md:4/9) explicitly keeps the PQ-consensus flip "founder-gated and audit-gated," i.e. not live. No doc implies post-quantum consensus is live.

  5. 273k TPS labeled a ceiling, never a live/measured rate. CONSISTENT. AERE-BENCHMARK-REPORT.md:42/49/55/61/81/372 repeatedly calls it an "architectural ceiling / design maximum / theoretical maximum," explicitly states "There is no testnet measurement that validates 273,000 TPS for L1," and separates it from the Block-STM harness figure (~247k-270k at gas=80, called a coincidence not a validation). AERE-REPRODUCIBLE-BUILDS.md:244 states "273,000 TPS is a synthetic design ceiling, not a measured mainnet number." No doc presents it as a live or measured rate. No contradiction.

CONSISTENCY VERDICT: No contradictions found on any of the five invariants. (The docs contain a number of honest [VERIFY] / [MEASURE] markers flagging open verification items, e.g. EIP-1559 base-fee disposal, EIP-7939 CLZ activation height, EOF-off confirmation. These are self-disclosed open items, not internal contradictions.)

SUMMARY

  • Compile: GREEN. 339 files compiled successfully, all new contracts present, warnings only.
  • Tests: GREEN. 118 passing, 1 pending (expected EIP-2537-present skip), 0 failing across all 10 new test files.
  • Consistency: no contradictions on burn, precompile bands, consensus params, PQC scope boundary, or the 273k TPS ceiling framing.