For Regulated Finance

Every signature that secures a public blockchain today rests on elliptic-curve cryptography, and its retirement is already on a regulator's calendar. NIST deprecates the classical 112-bit schemes after 2030 and disallows them after 2035 (IR 8547); the US federal migration mandate (OMB M-23-02) and the EU's coordinated roadmap run on the same clock. For a bank, a central securities depository, or a payment institution, the question is no longer whether to migrate a settlement system to post-quantum cryptography, but how to show a supervisor, an auditor, and a board that the work is real.

What you can show them

Chain 2800 is a public settlement ledger where that evidence already exists and can be checked. Since block 13,014,000, every anchor block binds a certificate of Falcon-512 validator signatures under the block hash itself, at an enforced minimum of seven per anchor block, as many as the 2f+1 quorum of the ten validators, since block 20,715,632 (2026-09-29; below block 24,148,752 the seals proved those validators signed the block, not that it was decided, per the AIP-22 erratum of 2026-10-01, and from that block a certificate that carries the quorum of one round proves the decision; three from 2026-08-14, six from block 14,961,456 on August 21, 2026). Five post-quantum precompiles run natively: four signature verifiers (Falcon-512, Falcon-1024, ML-DSA-44, SLH-DSA-128s) and the SHAKE256 hash function (corrected 2026-10-27: this sentence called all five NIST post-quantum verifiers). Since 2026-08-14, consensus does not finalize an anchor block (every 32nd) without at least three of the then nine valid post-quantum validator seals (raised at block 14,961,456, August 21, 2026, to six seals, then as many as the QBFT quorum of nine; from 2026-09-11 the set was ten and six sat above f+1 but below its quorum of seven, until block 20,715,632, on 2026-09-29, raised the enforced minimum to seven, as many as the quorum of the ten validators) (corrected 2026-08-19: not every block). None of this is a slide: it is a set of blocks your own team verifies against a public endpoint.

The engagement starts with verification, not slides

Your crypto-agility team downloads a single-file verifier, runs one command, and watches it recompute the binding digest independently from raw bytes. Then it fails on purpose, on pre-enforcement history and on a tampered domain, so you know the check can say no. Only after your team has seen the proof with its own eyes do we map your settlement flows onto post-quantum authorization together. The chain runs Ethereum's Prague and Osaka EVM rules (one exception: the EIP-4788 beacon-roots contract has no code), so your existing tooling and wallets carry over.

Three ways to work with us

Post-quantum migration testbed. Timed access for your team to exercise Falcon, ML-DSA, and SLH-DSA on a live public chain, with a reproducible conformance report for your regulator; see a sample report, generated by the same toolkit you can run yourself. A private post-quantum ledger. The same QBFT-plus-post-quantum stack, deployed for you, with two independently built clients. A quantum-safe tokenization pilot. Your asset, tokenized, with post-quantum evidence in the block record, not only at the application layer.

Honest boundaries, stated up front

Since 2026-08-14 every 32nd block (every 128th from block 17,225,968 to block 20,746,736, 2026-09-05 to 2026-09-29) on chain 2800 (an anchor block) does not finalize without a certificate of at least three valid Falcon-512 validator seals (f+1 of the nine validators of that time) (raised at block 14,961,456, August 21, 2026, to six seals, then as many as the QBFT quorum of nine; from 2026-09-11 the set was ten and six sat above f+1 but below its quorum of seven, until block 20,715,632, on 2026-09-29, raised the enforced minimum to seven, as many as the quorum of the ten validators) bound under its block hash; QBFT finalizes every block, whose votes every validator attributes, since block 24,300,000 (AIP-22 stage 4), only through their verified post-quantum seals (since block 25,080,000, AIP-22 stage 5, headers no longer carry ECDSA commit seals and are admitted on the Falcon-512 seal of their proposer alone; a commit still carries the ECDSA commit seal of its validator as an additional check). (Correction 2026-08-19: the earlier statement that from block 14,050,000 every block required a six-of-nine post-quantum quorum to finalize is withdrawn; the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules and changed no enforcement.) All ten validators are Foundation-operated while the independent-operator program is built, so the chain is not yet decentralized and we do not describe it that way. No external security audit has been completed; the first one is planned after the remaining consensus stages of AIP-22, no firm is engaged and no date is set (see /audits.html; corrected 2026-10-27: this sentence said an audit is on the roadmap with a date). Each of these is a real limitation, published, and each is a step we are taking in the open. We would rather you learn them from us than from a hostile reader.

curl -O https://aere.network/tools/verify-anchor.mjs -O https://aere.network/tools/mpt.mjs -O https://aere.network/tools/falcon512.mjs -O https://aere.network/tools/registry-v3.mjs -O https://aere.network/tools/package.json && npm install
node verify-anchor.mjs
# VERIFIED: 20/20 anchor blocks carry a post-quantum certificate
# bound under the block hash, every seal a valid falcon-512 or slh-dsa-sha2-128s signature
# (it also checks the minimum per scheme: 7, as many as the quorum, since block 20,715,632).

# The full toolkit: precompiles vs NIST vectors, block interval,
# validator set, contract fingerprints. Zero dependencies. Run the
# self-test first: it plants 21 defects and must catch every one.
curl -O https://aere.network/tools/verifica-lantul.tar.gz
tar -xzf verifica-lantul.tar.gz && cd verifica-lantul
node autotest.mjs   # prove the toolkit can say NO
node verifica.mjs   # then a green run means something