Payments That Stay Settled
A payment on chain 2800 is final in about half a second, there is no reorg to undo it, and since block 14,050,000 it settles under post-quantum validator signatures. The receipt is built to stay provable across the migration NIST has scheduled for classical cryptography.
In payments, the word settled usually comes with fine print. A card authorisation clears in seconds and can be reversed for months. On probabilistic blockchains, a merchant waits a chosen number of confirmations and accepts the residual risk that the ledger reorganises underneath them. Chain 2800, a public EVM Layer 1, removes the fine print: a block is final the moment a quorum of six of nine validators signs it, about half a second after your transaction enters it (block time measured at 0.53 s today), and the consensus has no mechanism for taking a finalized block back.
No consensus chargebacks
On a probabilistic chain, finality is a probability that improves with time, and a reorg is the ledger itself issuing a chargeback: blocks both sides treated as settled are replaced, and every payment inside them is unwound. Processors compensate with confirmation-depth policies, reorg monitoring, and float held against the chain changing its mind. Chain 2800 uses QBFT consensus, where finality is a property of the protocol rather than a probability: once six of nine validators have signed a block, it is final, and there are no reorgs by design. Deterministic sub-second finality is the performance claim of this page, and it is the one that matters for money. When the block closes, the payment is settled, and settled does not decay.
A receipt that does not expire
Since block 14,050,000, consensus on chain 2800 is hybrid: no block finalizes without a quorum of Falcon-512 post-quantum validator signatures, with classical ECDSA retained alongside. On top of that, every 32nd block header carries a certificate of validator Falcon seals bound under the block hash, live since block 13,014,000 and enforced at a minimum of three seals since 2026-08-14.
For a processor, this is about the paperwork, not the plumbing. The settlement records you show an auditor, a regulator, or a counterparty in a dispute are only as durable as the signatures beneath them, and for the classical signatures securing most chains, NIST's post-quantum migration guidance (IR 8547, initial public draft 2024) schedules deprecation after 2030 and disallowance after 2035. A payment settled on chain 2800 sits under a post-quantum anchor, so demonstrating years from now that it happened, exactly as recorded, does not rest on cryptography that has since been retired. For retention obligations measured in decades, that is the difference between a receipt and a receipt with an expiry date. The same property, applied to documents rather than payments, is described on the notarization page.
Integration is the boring part, by design
Chain 2800 offers full EVM compatibility at Pectra plus Fusaka parity. MetaMask connects, ethers works, hardhat and foundry compile and deploy without modification. If your team has integrated any EVM chain, they have integrated this one; the post-quantum layer lives inside consensus and asks nothing of your application code. Contracts that want post-quantum verification directly can call the five NIST verifier precompiles live since block 9,189,161, validated against official NIST vectors. The native token is AERE, with a fixed supply of 2.8 billion set at genesis and no new minting. Start at the developer hub, and read the architecture page for how the pieces fit.
Honest boundaries
All nine validators are operated by the Foundation today. The chain is not yet decentralized and we do not describe it that way; an independent-operator program is being built. There is no completed third-party security audit yet; it is on the roadmap. We do not publish throughput figures; deterministic sub-second finality is the performance claim we stand behind. And this page describes what the chain can do and how we engage, not a deployed retail payments product: we do not offer card programs, banking services, or custody.
Check the settlement layer yourself
# verify the post-quantum anchor on the live chain npm install @noble/hashes curl -O https://aere.network/tools/verify-anchor.mjs node verify-anchor.mjs # or fetch the full independent suite: 35 checks curl -O https://aere.network/tools/verifica-lantul.tar.gz tar -xzf verifica-lantul.tar.gz
Three ways to work with us
A payments pilot. A scoped engagement with our team: pick one bounded settlement flow, run it on chain 2800, and measure finality and operational load together before anything larger is committed.
An integration. Your engineers build against the chain directly, with the EVM tooling they already use. The developer hub has the network details and examples, and we answer questions while you build.
Independent verification. Do not take this page's word for anything. Run the anchor verifier, run the 35-check suite, read the research library and the sample conformance report, and only then talk to us.