Talero Programmable Layer 1

Live public testnet

A programmable blockchain with explicit cryptographic boundaries.

Talero combines EVM execution with component-level post-quantum capabilities. The current runtime posture is mixed: classic transactions remain allowed, the native PQ route is optional, and strict BFT finality is scheduled rather than active.

Compatibility without camouflage. Classic Ethereum transactions use ECDSA secp256k1 and are not post-quantum. Native type 0x06 uses ML-DSA-65 and Talero-specific tooling when that route is enabled.

See the chain live Build on Talero
  • Component-level post-quantum design. The observed node uses hybrid-required P2P transport and implements ML-DSA-65 transaction, validator and attestation formats.
  • Fully programmable. REVM execution supports Ethereum contracts, MetaMask, ethers and viem on the classic route.
  • Auditable rule sets. Consensus manifests make cryptographic rules and coordinated transitions machine-verifiable by conforming nodes.
Talero combines native ML-DSA signing, classic Ethereum compatibility and verifiable attestations.
Distinct transaction and verification paths on one programmable public testnet.

Why Talero

Post-quantum components without hiding the classical boundary.

Talero keeps Ethereum programmability while adding separate PQ-capable transaction, transport and attestation mechanisms. Each claim applies to a named component and its current runtime state.

01 · Component-level PQ

Verify each layer.

The observed node’s P2P sessions require hybrid X25519 and ML-KEM-768 key establishment with ML-DSA-65 authentication. Native type 0x06, validator identity and BFT evidence formats use ML-DSA-65.

Classic transactions remain allowed. PoQ is advisory, and strict BFT finality is scheduled at height 115200 rather than active on the current pre-activation chain.

02 · EVM programmability

Bring your Ethereum tools.

Talero runs EVM contracts through REVM. Legacy, EIP-2930 and EIP-1559 transactions work with MetaMask, ethers and viem through the classic ECDSA route.

03 · Cryptographic auditability

Turn rule sets into evidence.

The consensus manifest records cryptographic algorithms, schemes, roles and coordinated transitions. Curated public summaries describe the integration boundary without publishing private topology or an exhaustive control-plane inventory.

Explore the Talero CBOM →

Network, live

Inspect the public testnet as it moves.

The displayed head comes from the Explorer’s indexed API with an automatic JSON-RPC fallback. Explorer REST, public JSON-RPC and controlled node REST are separate surfaces.

Checking explorer head
Network stagePublic testnetNo mainnet claim.
Block heightCheckingIndexed head with freshness check.
Chain ID231846Validated before wallet configuration.
Target block time8 secondsProtocol target, not a latency guarantee.

Two trust models

Ethereum compatibility today. A runtime-gated native PQ route.

The effective policy is classic_allowed. Both address families share one WorldState, but only the native type 0x06 format provides ML-DSA-65 transaction authorization.

Classic Ethereum route

Use the existing ecosystem.

ECDSA secp256k1 powers legacy, EIP-2930 and EIP-1559 transactions. MetaMask, ethers and viem work on this route. Its signature remains classical.

Native Talero route

Confirm availability before signing.

Type 0x06 uses ML-DSA-65 and Talero-specific tooling. The node implements this format, but the observed public capability reports it as optional rather than mandatory; applications must check runtime policy and must not silently fall back to ECDSA.

Compare transaction paths See the current PQ posture

Start building

Connect the classic route. Verify optional features at runtime.

The classic ECDSA route plugs into Ethereum tooling immediately. Native type 0x06 requires Talero-specific tooling and a compatible runtime policy.

Network Talero Public Testnet
Chain ID 231846 (0x389a6)
RPC URL https://rpc.talero.info/rpc
Symbol TLRO
Explorer explorer.talero.info
Faucet faucet.talero.info
Open developer docs 

curl -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

Post-quantum readiness has moved from roadmap to deadline.

Federal policy now ties migration to dated milestones and machine-assessable cryptographic inventories. Talero implements inventory and transition mechanisms while documenting the current classical, optional and inactive boundaries explicitly.

Executive Order 14412

2030 is an operating deadline.

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 →
CNSA 2.0

New national-security acquisitions change in 2027.

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 →
CBOM + crypto agility

Inventory becomes infrastructure.

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

Publish stable facts. Verify changing state live.

Source inventories, deployment policies and public exposure are distinct. Talero’s public documentation now describes stable integration boundaries and directs clients to runtime state for changing capabilities.

Stable public parameters

  • Public testnet chain ID 231846 (0x389a6).
  • Gas target 45,000,000; block gas limit 90,000,000.
  • Maximum supply 1,000,000,000 TLRO with 18 decimals.
  • Target block time 8 seconds.

Current security boundaries

  • Classic EVM transactions remain ECDSA and are not post-quantum.
  • Native ML-DSA-65 transaction authorization is optional under classic_allowed.
  • Strict BFT finality is scheduled at height 115200; current bootstrap_lag is not payout-grade finality.
  • PoQ remains advisory, non-consensus and non-blocking.

RPC

Public JSON-RPC is method-gated, cost-aware and limited to batches of five calls.

Explorer

Indexed REST data has explicit privacy, freshness and degraded-state semantics.

PQ transactions

Native type 0x06 is implemented but runtime-gated and not required.

Finality

Read the semantic class; a lag checkpoint is not strict BFT settlement.

Build with a security model you can verify.

Start with the transaction paths, current PQ posture, CBOM architecture, public APIs, authenticated mining and finality semantics.

Open technical documentation Read the CBOM architecture