Precompile

A precompile is a function built directly into the node software and exposed at a fixed address. To a smart contract it looks like any other contract: you call the address, pass input, read output. The difference is that the code behind it is native, not EVM bytecode, so operations that would be impractical to express as bytecode, such as verifying signatures over large keys, run at practical cost. Every EVM chain ships with a base set of precompiles (ecrecover is the original example), and that shared set is part of what EVM compatibility means.

Chain 2800 extends that set. Five post-quantum precompiles have been live since block 9,189,161, at addresses 0x0AE1 through 0x0AE5, covering the Falcon-512, ML-DSA, and SLH-DSA signature families. Each was validated on-chain against NIST test vectors, so any contract on chain 2800 can verify a post-quantum signature today.

One boundary matters here. A precompile is a capability, not a guarantee: it verifies whatever it is given. Consensus signatures on chain 2800 are classical ECDSA secp256k1, and calling a post-quantum verifier from an ordinary transaction does not, by itself, make the calling account post-quantum safe. What binds post-quantum cryptography to the chain itself is the post-quantum anchor: since block 13,014,000, every 32nd block header carries a seal certificate of at least 3 Falcon-512 signatures from the validators over the parent block, with a 32-byte digest of that certificate inside the data covered by the block hash.