Signer Registry

A signer registry answers a question that signature verification alone cannot: not "did some key sign this?" but "did the right key sign this?". A signature proves possession of a private key; only a registry, a published binding between each validator and its public key, turns that into proof that a specific validator signed. Without one, a certificate of post-quantum signatures floats free, because anyone can generate keys and sign anything.

On chain 2800 the registry has nine entries, one per validator, each binding a validator address to its Falcon-512 public key. The registry is committed on chain: an immutable contract holds, in its storage, the keccak hash of the full registry contents. Immutable means what it says: the contract has no update path, so the commitment cannot be quietly replaced. Changing the bound set means publishing a new commitment, in the open, where anyone can see the change.

The registry is what the post-quantum anchor checks against. Since block 13,014,000, every 32nd block header carries a seal certificate of Falcon-512 signatures from the validators over the parent block, and a 32-byte digest of that certificate sits inside the data covered by the block hash. A signature counts toward the certificate only if its key appears in the registry. The threshold enforced today is at least 3 signatures per anchor block; in practice certificates carry 5.

One boundary, stated plainly: the consensus signatures behind finality are classical ECDSA secp256k1 today. The registry serves the anchor, not consensus voting.