Aere Cloud · chain-native post-quantum verification

Post-quantum signature verification, as an API.

Live NIST FIPS 204 / 205 Falcon Chain-native

Endpoint cloud.aere.network/v1/pq/verifyLive since block 9,189,161Chain 2800

Send a signature, a public key and a message; get back a verdict computed by a public blockchain’s own native precompiles: not by a library we run beside the API. Every answer carries the block height it was computed at and can be re-checked against the chain by anyone.

What you can verify

Scheme	Standard	Request fields
ml-dsa-44	NIST FIPS 204 (Dilithium)	publicKey, signature, message
slh-dsa-128s	NIST FIPS 205 (SPHINCS+)	publicKey, signature, message
falcon-512	Falcon (round 3)	publicKey, signedMessage
falcon-1024	Falcon (round 3)	publicKey, signedMessage

All fields are 0x-prefixed hex. The verdict names which precompile answered and at which block height, so it is reproducible against the public RPC.

A real exchange

POST https://cloud.aere.network/v1/pq/verify
x-api-key: ak2800.<your-address>.<secret>
{ "scheme": "ml-dsa-44", "publicKey": "0x…",
  "signature": "0x…", "message": "0x…" }

→ { "valid": true, "scheme": "ml-dsa-44",
     "precompile": "0x…0ae3", "block": 15220111, "chainId": 2800 }

# flip one bit of the signature and the chain returns valid:false

Why this is different from a library

Anyone can run a post-quantum verifier in their own process. What you cannot do elsewhere is have the verdict produced by a neutral public network, at a named block height, that a counterparty can independently reproduce. On Aere the verifiers are native precompiles, live on mainnet since block 9,189,161, validated against the official NIST known-answer and ACVP vectors in both directions. The verification does not rest on trusting our servers: it rests on the chain.

And the chain that answers is itself post-quantum-attested

Every 32nd block of chain 2800 (every 128th from block 17,225,968 to block 20,746,736, 2026-09-05 to 2026-09-29) does not finalize without a certificate of at least seven valid Falcon-512 validator seals bound under the block hash, as many as the quorum of the ten validators since block 20,715,632 (2026-09-29; the seals prove those validators signed the block, not that it was decided, per the AIP-22 erratum of 2026-10-01); the minimum was six before that, as many as the quorum of the nine validators of that time and, from 2026-09-11, below the ten-validator quorum of seven. So a verdict you anchor here lives on a network whose own consensus carries post-quantum evidence, proven and independently verifiable rather than asserted. Check it yourself with the verifier tool or the live verification page.

Use cases

Long-lived documents and signatures that must stay verifiable past the arrival of quantum computers.
Hybrid signing: attach a post-quantum signature beside a classical one, and verify both.
Compliance and audit trails where a neutral, reproducible verdict matters more than a private library’s word.

Get an API key Read the docs

Part of Aere Cloud. The precompiles are also callable directly from any contract on chain 2800; the API is the convenience layer over them.