AERE Network, Chain ID 2800

Verify quantum durability yourself

Five NIST post-quantum signature and hash precompiles run live on AERE mainnet. This page replays the published KAT and ACVP conformance vectors against them in your browser, with a read-only eth_call. No wallet. No keys. No writes. Every check is reproducible from your own node.

Honest scope

This proves account and application-layer post-quantum cryptography: the five precompiles at 0x0AE1 to 0x0AE5 verify NIST PQC signatures and compute SHAKE256 fully on-chain, so contracts and accounts on chain 2800 can adopt post-quantum signatures today.

Consensus is still classical ECDSA. AERE's QBFT block production and finality use classical secp256k1 signatures. A hybrid post-quantum consensus mode exists only on an isolated testnet and is audit-gated, not live. This page makes no claim about the consensus layer.

PQC precompiles

Conformance vectors

Verified live

Mismatched

Verified at block

Idle. The precompiles have been active since block 9,189,161.

How this works

Each vector is a hex blob captured from a NIST Known Answer Test or from the NIST Automated Cryptographic Validation Program. The page sends it as the calldata of a read-only eth_call to the precompile address. The signature precompiles return a 32-byte word: 0x00...01 accepts a valid signature, 0x00...00 rejects a tampered or malformed one. SHAKE256 returns the raw digest bytes. The page compares the live return against the expected output byte for byte, then shows you the exact curl so you can run the same call against https://rpc.aere.network or any AERE node yourself.

Vectors are loaded from a static in-repo fixture (/quantum-vectors.js), copied verbatim from the conformance suite. Nothing is fetched from a third party. Signature verification is a public operation, so none of this input is secret.

Loading conformance vectors,

Provenance and honest limitations

Vectors carry their source in each row: Falcon round-3 KATs, NIST ACVP ML-DSA (FIPS-204) and SLH-DSA (FIPS-205) internal test groups, and FIPS-202 SHAKE256 KATs. The full suite lives at aerenew/conformance/conformance-vectors.json and is the same set the AERE second-client conformance test replays byte for byte.
The signature precompiles verify a signature. They do not, by themselves, prove a message was signed by a specific party in your application. Binding a public key to an identity is the job of the contract or account that calls them.
On malformed, too-short, or wrong-length input the four signature precompiles always return a 32-byte zero word (reject), never empty. SHAKE256 returns empty (0x) when the output length is zero or the input is shorter than the 32-byte length prefix. Both behaviours are covered by vectors below and verified live.
This page reads the chain. It never signs, sends, or writes anything. The results depend only on the public state of chain 2800 and are identical from any node.

Precompiles: Falcon-512 0x0AE1 · Falcon-1024 0x0AE2 · ML-DSA-44 0x0AE3 · SLH-DSA-128s 0x0AE4 · SHAKE256 0x0AE5 · Verified contracts · Network status