Post-quantum architecture
Component-level PQ capabilities, with a mixed runtime posture.
Talero includes ML-DSA-65 and ML-KEM-based components, but the current public-testnet posture is not end-to-end post-quantum: classic transactions remain allowed, PoQ is advisory and validator finality is not active.
ML-DSA-65 components
Hybrid-required P2P
Classic transactions allowed
PoQ advisory
Do not collapse component claims into a network-wide guarantee. Check the transaction, transport and finality layers separately.
Observed public-testnet posture
| Layer |
Observed state |
Correct claim |
| P2P transport |
hybrid_required, active and ready on the observed node |
Node transport uses a hybrid PQ/classical handshake and authenticated encryption. |
| Transaction signatures |
classic_allowed; PQ optional, classic allowed |
Native ML-DSA-65 transaction support exists, but standard ECDSA transactions remain valid. |
| PoQ |
Advisory, degraded, non-consensus and non-blocking |
PoQ adds evidence; it does not decide block validity or finality. |
| Validator finality |
Inactive before the scheduled strict-BFT phase |
ML-DSA-65 formats are implemented, but there is no current active PQ finality guarantee. |
| EVM verifier |
Experimental precompile at 0x0000000000000000000000000000000000000903
|
Contracts can verify ML-DSA-65 inputs; classic accounts do not become PQ accounts. |
Two transaction trust models
Classic Ethereum formats use ECDSA secp256k1 and standard Ethereum tooling. The native type 0x06 format uses ML-DSA-65 and Talero-specific tooling. Both affect the same WorldState, but they do not provide the same cryptographic assurance. Applications that require PQ authorization must verify that the native route is enabled for their deployment and must not silently fall back to ECDSA.
Other PQ components
Validator registration proofs, BFT message schemas, checkpoint attestations and slashing-evidence formats include ML-DSA-65 designs. TaleroHash uses Keccak-256 plus a memory component for proof of work. These facts describe individual mechanisms, not a blanket claim that every account, transaction, node role and settlement path is quantum-safe today.
How to verify the effective state
Use talero_getPqNodeStatus for the aggregate posture, talero_txCapabilities for the effective transaction-signature policy, talero_poqStatus for PoQ semantics and talero_finalizedHead for finality class. Treat a mixed or degraded result as an explicit limitation.
