EVM integration
Bring Ethereum tools. Add native post-quantum authorization.
Talero keeps the EVM developer experience and adds a first-class ML-DSA-65 transaction route beside it.
REVM execution activeMetaMask · ethers · viemNative 0x06One WorldState
Public-safe is not unrestricted. Privacy, safe-mode, read-only, quota, role and gateway policies can still mask or deny a listed surface.
The bridge and the destination
| Path | Formats | Signature | Tooling | Quantum posture |
|---|
| Classic Ethereum | Legacy, EIP-2930, EIP-1559 | ECDSA secp256k1 | MetaMask, ethers and viem | Compatible, not post-quantum |
| Native Talero | Type 0x06 | ML-DSA-65 | Talero-specific SDK required | Post-quantum transaction signature |
Both paths are active from the first block under classic_allowed. They use two address families, bind each signature to one transaction type and update the same WorldState.
ML-DSA-65 does not provide Ethereum-style signer recovery. Type 0x06 is therefore a native Talero transaction rather than a standard Ethereum transaction, and standard Ethereum wallets do not produce it.
Programmability is the differentiator
Talero runs EVM contracts through REVM. Existing Ethereum contracts and developer tools stay useful on the classic route; applications that need post-quantum transaction authorization can add the native route without moving to a separate ledger.
ML-DSA-65 verification precompile
The experimental prototype verifier is available at 0x0000000000000000000000000000000000000903. Its cost is 120,000 gas plus 32 gas per calldata byte. The maximum message is 4,096 bytes and the maximum input is 16,384 bytes.
REVM spec: PRAGUE_EOF; KZG (0x0A) and BLS12-381 (0x0B–0x13) precompiles are unavailable in the current release, and integrators must verify precompile return length, not call success alone.
One explicit account boundary
Classic EVM accounts remain secured by ECDSA secp256k1. Applications that require a post-quantum transaction signature use the separate native 0x06 path.
