Build on Talero
Ethereum-compatible execution with explicit security boundaries.
Technical documentation for the Talero public testnet: EVM integration, authenticated pool mining, indexed chain data and component-level post-quantum capabilities.
Public testnet
Chain ID 231846
Runtime-gated surfaces
Mixed PQ posture
Capabilities are deployment-specific. Source inventories, access profiles and live public exposure are distinct contracts.
One chain, distinct trust models
Talero runs EVM contracts and permits classic Ethereum ECDSA transactions. It also implements a native type 0x06 ML-DSA-65 transaction format. The current effective policy is classic_allowed: the PQ format is not mandatory and standard EVM accounts remain classical.
Post-quantum properties are documented per component. The observed P2P transport is hybrid-required, while PoQ remains advisory and strict validator finality is scheduled for height 115200 rather than active on the current pre-activation chain.
Documentation map
Public-testnet endpoints
| Service |
Endpoint |
Purpose |
| JSON-RPC |
https://rpc.talero.info/rpc
|
Filtered node reads; JSON-RPC POST only |
| Explorer |
https://explorer.talero.info
|
Blocks, transactions and indexed public data |
| Wallet |
https://wallet.talero.info
|
Local account and transaction workflows |
| Pool |
https://pool.talero.info
|
Mining status and authenticated miner dashboard |
| Faucet |
https://faucet.talero.info
|
Testnet funds subject to service protections |
Stable integration parameters
| Parameter |
Value |
Meaning |
| Chain ID |
231846 / 0x389a6
|
Validate before signing. |
| Target block time |
8 seconds |
Protocol target, not a latency guarantee. |
| Gas target / block limit |
45,000,000 / 90,000,000 |
Current runtime parameters. |
| Epoch |
1,000 blocks |
Consensus parameter. |
| Maximum supply |
1,000,000,000 TLRO |
18 decimals. |
Publication boundary
These pages document stable public endpoints, user workflows and security semantics. They intentionally exclude secret material, private topology, internal diagnostics, back-office feature names, administrative controls and exhaustive deployment capability maps.
This is a public testnet, not a mainnet, regulatory certification or production-readiness claim.