Post-quantum architecture

Post-quantum from genesis.

ML-DSA-65 is part of Talero's validator, BFT, checkpoint, P2P and native transaction architecture from the first block.

ML-DSA-65Native 0x06Encrypted P2PTaleroHash

Public-safe is not unrestricted. Privacy, safe-mode, read-only, quota, role and gateway policies can still mask or deny a listed surface.

Built in, not bolted on

Talero produces attestations whose verification remains valid after the quantum transition.

The chain does not depend on a future migration to introduce ML-DSA-65 into its validator identity, BFT evidence, checkpoints, P2P authentication or native transaction format. Each claim maps to a concrete component.

Complete coverage map

ComponentCryptographyWhat it delivers
Validator identity and registration proof of possessionML-DSA-65Post-quantum validator authorization
HotStuff proposals, votes and quorum certificatesML-DSA-65Post-quantum BFT attestations
Slashing proofs and finality certificatesML-DSA-65Post-quantum evidence formats
Checkpoint notaryML-DSA-65Post-quantum checkpoint attestations outside consensus
P2P transportHybrid X25519 + ML-KEM-768 key exchange, ML-DSA-65 authentication and ChaCha20-Poly1305 after key exchangeAuthenticated and encrypted node transport
EVM verification precompileML-DSA-65 at 0x0000000000000000000000000000000000000903Experimental prototype verifier
Native transaction type 0x06ML-DSA-65Post-quantum signature, active from the first block
PoW TaleroHashKeccak-256 plus memoryQuantum-resistant work function
Classic Ethereum transactionsECDSA secp256k1Ethereum compatibility; classical signature

Compatibility and native PQ coexist

Under classic_allowed, classic ECDSA transactions and native 0x06 ML-DSA-65 transactions use two address families and one WorldState. The classic route brings MetaMask, ethers and viem; the native route makes the transaction signature itself post-quantum.

PoQ stays advisory by design

PoQ certification is advisory, non-consensus and non-blocking. It provides independently verifiable evidence without deciding block validity or replacing the canonical finality read.

The claim has precise edges

  • Classic Ethereum transactions and standard EVM accounts remain ECDSA secp256k1.
  • The experimental EVM verifier does not change a classic account's signature scheme.
  • The BFT finality architecture is tested and ready for activation; strict activation is not armed in the deployed public testnet release.