Glossary
12 terms
Twelve terms that explain chain 2800, each grounded in a measurement you can re-run yourself.
- Post-Quantum Anchor
Anchor headers on chain 2800 (every 32nd block from 13,014,000; every 128th from 17,225,968 to 20,746,736) bind a certificate of post-quantum validator seals under the block hash via a 32-byte digest: Falcon-512, and SLH-DSA-SHA2-128s as well since 2026-09-04 (at every 128th block since 2026-09-29). - Validator
A validator is one of ten nodes that propose and sign blocks on chain 2800, where a block becomes final once seven of them have signed it. - Finality
On chain 2800 a block is final the instant seven of ten validators commit it under QBFT, so for a validator finality arrives with the block itself, in well under a second, and from block 25,080,000 (AIP-22 stage 5) a node outside consensus reads it as final once the next anchor covers it. - Precompile
A precompile is a native function at a fixed address; on chain 2800, five post-quantum precompiles, four signature verifiers and the SHAKE256 hash function, have run this way since block 9,189,161. - QBFT Consensus
The vote-based consensus behind chain 2800: ten validators, a quorum of seven, one block roughly every 0.62 s, and, for a validator, finality the moment a block appears. - Falcon-512
The lattice-based signature scheme, selected by NIST for post-quantum standardization, that chain 2800 uses to anchor its block history. - Seal Certificate
A bundle of post-quantum validator signatures (Falcon-512, and SLH-DSA since 2026-09-04) over a block, with a 32-byte digest sealed under the block hash on every 32nd header of chain 2800. - Base Fee Floor
A consensus-enforced minimum base fee: chain 2800 rejects any block header whose base fee falls below the floor, keeping spam costly and fees predictable. - Block Header
A block header is what the block hash commits to; on chain 2800 every 32nd header since block 13,014,000 also binds a post-quantum certificate digest. - Signer Registry
The list binding each of chain 2800's ten validators to a Falcon-512 public key: committed as a keccak digest in an immutable contract up to the epoch of block 18,082,816, and pinned by its hash in the node configuration since the version-3 epoch of block 20,836,228. - Client Diversity
Two independently written clients validate chain 2800, so a bug in one implementation becomes a visible disagreement instead of a silent network-wide fault. - EVM Compatibility
Chain 2800 runs the EVM under Ethereum's Prague and Osaka rules, with one named exception; contracts and tooling work unchanged, and post-quantum additions live in precompiles, the header and one extra transaction type.
Next up
The post-quantum stack