aere-network/aere-docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
main
aere-docs/README.md
Aere Network 0d253ba08a 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:31:57 +03:00

3.8 KiB
Raw Permalink Blame History

aere-docs

The honest engineering and research documentation set for Aere Network.

This repository is the written half of the Aere Network "verify yourself" core. It collects the protocol specification, the engineering and security spec, the EIP compatibility matrix, the post-quantum cryptography and governance documents, the STARK verifier port specifications (with their explicit caveats), the formal verification coverage reports, the reproducible-build and cross-client determinism documents, and the reproducibility manifest.

Scope, stated up front

Aere Network runs post-quantum signature verification natively on mainnet: Falcon-512 (0x0AE1), Falcon-1024 (0x0AE2), ML-DSA-44 (0x0AE3), SLH-DSA-128s (0x0AE4) and SHAKE256 (0x0AE5) have been live as precompiles since block 9,189,161. You can call them yourself against https://rpc.aere.network without asking us for anything.

Consensus on chain 2800 is classical secp256k1 ECDSA QBFT. The post-quantum work lives at the signature, precompile, account and transport layers. Nothing in this repository makes the consensus post-quantum, and nothing in it should be read as claiming so. Where you see post-quantum consensus discussed, it is research about what a future activation could look like, not a description of the running chain.

Two further limits worth knowing before you judge anything else here:

  • 0x0AE6 (ML-KEM-768) and 0x0AE7 (Falcon HashToPoint) are testnet only. They are not active on mainnet.
  • The on-chain zero-knowledge verifiers are classical BN254. They are broken by Shor's algorithm like any other elliptic-curve construction, and we do not describe them as quantum-safe.

The network is operated by seven Foundation-run validators, so its Nakamoto coefficient is effectively one today. That is a real limitation, it is on the roadmap, and it is not fixed by any code in this repository.

Start here

  • REPRODUCE.md the single reproducibility manifest. It lists real paths, real commands, and real expected outputs so a third party can re-run the tests, the formal models, the KATs, and the benchmarks and get the same results. Every quantitative claim carries an honesty tag ([FRESH], [CITED], or [MEASURE]).
  • AERE-PROTOCOL-SPECIFICATION.md the protocol specification.
  • AERE-ENGINEERING-SECURITY-SPEC.md the engineering and security spec.
  • AERE-ARCHITECTURE-MAP.md the architecture map.

Contents

  • Compatibility and validation: AERE-EIP-COMPATIBILITY-MATRIX.md, AERE-NIST-VALIDATION-STATUS.md, AERE-CROSS-CLIENT-DETERMINISM.md, AERE-REPRODUCIBLE-BUILDS.md, AERE-BENCHMARK-REPORT.md.
  • Post-quantum: AERE-POST-QUANTUM-GOVERNANCE.md, AERE-QUANTUM-SAFE-NETWORKING.md, AERE-QUANTUM-MIGRATION*.md, AERE-PQ-*.md, AERE-XMSS-*.md, AIP-PQ-TX-2026-07-18.md.
  • STARK verifier port: the AERE-STARK-*.md series, including AERE-STARK-DOC-CAVEAT-SWEEP.md which records the Hypercube and other caveats plainly.
  • Formal verification: AERE-CERTORA-FORMAL-VERIFICATION.md, AERE-TLA-FORMAL-SPEC.md, AERE-FORMAL-FINAL-COVERAGE.md, AERE-FORMAL-BROADEN-REPORT.md, AERE-FORMAL-EXTENSION-MONEY-CONTRACTS.md, AERE-FAULT-INJECTION-HARNESS.md.
  • Security review: AERE-SECURITY-REVIEW-NEW-CONTRACTS.md, AERE-SECURITY-FIXES.md.
  • Process and delivery: AERE-AIP-PROCESS-AND-INDEX.md, AERE-NEW-CONTRACTS-DEPLOY-RUNBOOK.md, AERE-DEPLOY-RUNBOOK-SUMMARY.md, AERE-BUILD-LOOP-SUMMARY-2026-07-19.md.

What is deliberately not here

Internal operations material, business and press strategy, infrastructure runbooks that name hosts, funding and cost documents, and the mainnet-activation and node-provisioning runbooks are intentionally excluded. Infrastructure IP addresses and host identifiers that appeared in a few in-scope documents were redacted before staging.

License

Documentation is provided under MIT. See LICENSE.