Live public testnet
The EVM-compatible Layer 1 where post-quantum cryptography secures the chain from the first block — no migration, no retrofit.
Compatibility without camouflage. Classic Ethereum transactions remain ECDSA secp256k1 and are not post-quantum. Talero adds a native ML-DSA-65 transaction route beside them — two address families, one WorldState.
Why Talero
A signature-only store of value cannot run your contracts. Talero can. Bring Ethereum tooling to a chain designed around post-quantum cryptography from its first block.
ML-DSA-65 is wired into validator identity, registration proofs, HotStuff votes and quorum certificates, slashing evidence, checkpoint attestations and the native 0x06 transaction path. P2P sessions combine hybrid key exchange, ML-DSA-65 authentication and encrypted application traffic.
The BFT finality architecture is tested and ready for activation; strict activation is not armed on the public testnet.
Talero runs EVM contracts through REVM. Classic legacy, EIP-2930 and EIP-1559 transactions work with MetaMask, ethers and viem. Developers keep the ecosystem they know while gaining a native post-quantum route when the transaction signature itself must endure.
The consensus manifest acts as a machine-verifiable cryptographic inventory — a CBOM each node confirms. Algorithms, schemes, roles and coordinated transitions become auditable network facts, without publishing operational secrets or release-identifying values.
Explore the Talero CBOM →Network, live
The explorer head is read live. The runtime publishes explicit chain parameters and classified public surfaces across RPC and REST.
Checking explorer headThe bridge and the destination
Under classic_allowed, both signature families are active and write to the same WorldState. Choose compatibility or native post-quantum authorization per transaction path.
ECDSA secp256k1 powers legacy, EIP-2930 and EIP-1559 transactions. MetaMask, ethers and viem work on this route. Its signature remains classical.
Type 0x06 has been active since the first block. ML-DSA-65 has no Ethereum-style signer recovery, so this route uses a Talero-specific SDK and is not a standard Ethereum transaction.
Start building
The classic route plugs into Ethereum tooling immediately. The native 0x06 route uses a Talero-specific SDK for ML-DSA-65 authorization.
0x389a6)https://rpc.talero.info/rpccurl -s -X POST https://rpc.talero.info/rpc \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'Why now
Federal policy now ties migration to dated milestones and machine-assessable cryptographic inventories. Talero starts with the cryptography and the inventory already inside the chain architecture.
Signed June 22, 2026, the order sets December 31, 2030 for PQC key establishment on federal high-value and high-impact systems, followed by digital signatures in 2031. It also directs public guidance for minimum CBOM elements.
Read the order →From January 1, 2027, new acquisitions for National Security Systems must be CNSA 2.0 compliant unless otherwise noted. The transition window is already open.
Read the NSA guidance →NIST frames cryptographic discovery, inventory and replaceability as the foundation of migration. Talero makes a verifiable cryptographic inventory part of the consensus design.
See how Talero proves it →Evidence over slogans
Regenerated runtime contracts and adversarial internal auditing keep the public claims tied to what the node actually implements.
265 inventoried methods; 155 default public reads.
91 inventoried routes; 56 classified public.
Native ML-DSA-65 type 0x06 from the first block.
Advisory, non-consensus and non-blocking.
Go from the transaction paths to the complete cryptographic map, CBOM architecture, public APIs, P2P transport and consensus semantics.