Seal Certificate
A bundle of Falcon-512 validator signatures over a block, with a 32-byte digest sealed under the block hash on every 32nd header of chain 2800.
A seal certificate is a package of signatures in which several validators independently attest to the same block. One signature proves that one machine endorsed the block; a certificate proves that a defined minimum of the validator set did. What makes a certificate useful is not the signatures alone but how it is bound to the chain: if it could be detached or swapped without changing the block hash, it would prove nothing to a later reader.
On chain 2800, the seal certificate is the carrier of the post-quantum anchor. Since block 13,014,000, every 32nd block header carries a certificate of Falcon-512 signatures from the validators over the parent block. The certificate travels in the header, and a 32-byte digest of it sits inside the data covered by the block hash. Change or remove one signature and the certificate no longer matches the digest sealed under the hash, so the header fails validation.
The rule enforced today requires at least 3 signatures per anchor block, drawn from the 9 entries of the on-chain signer registry; in practice certificates carry 5, the configured cap. The certificate is an attestation layer, not the consensus itself: finality on chain 2800 is decided today under QBFT with classical ECDSA secp256k1 signatures, and AERE does not claim post-quantum consensus. The certificate records, in a signature family designed to resist quantum attack, which validators stood behind each anchored block.
Verify it yourself
Verify it yourself: POST {"jsonrpc":"2.0","method":"eth_getBlockByNumber","params":["0xC693F0", false],"id":1} to https://rpc.aere.network. Height 0xC693F0 is block 13,014,000, an anchor height: the returned extraData decodes to the Falcon-512 certificate, and its first 32-byte field is the digest covered by the block hash. A non-anchor header nearby decodes to a plain vanity string instead.