For Regulated Finance
The public settlement ledger where your quantum-safe migration story is already true, already checkable, and ready for a regulator.
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 the public settlement ledger where that story is already true and already checkable. 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 three per block. Five NIST post-quantum verifiers run as native precompiles. The blocking post-quantum consensus mode is armed. 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 is EVM at Ethereum parity, so your existing tooling, wallets, and audits 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
Consensus signatures on chain 2800 are classical ECDSA today, with the blocking post-quantum mode armed behind a coordinated activation height. All nine 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; one 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.
Have your team check us first
npm install @noble/hashes curl -O https://aere.network/tools/verify-anchor.mjs node verify-anchor.mjs # VERIFIED: 20/20 anchor blocks carry a post-quantum certificate # bound under the block hash, each with at least 3 Falcon-512 seals. # 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
Subject line "Post-quantum migration testbed" reaches the right person directly. Or start with the Foundation.