Capability guide

Public capabilities with explicit runtime boundaries.

This guide covers integration-relevant behavior. It intentionally omits internal controls, back-office feature names and operational dependencies.

EVM execution Authenticated mining Mixed PQ posture Scheduled BFT

Capability is not availability. The live gateway, service authentication and current network height still decide what an application can use.

Integration matrix

Capability Current public-testnet posture Boundary
EVM execution Active Method exposure and writes remain deployment-gated.
Classic Ethereum transactions Allowed ECDSA secp256k1 is compatible, but not post-quantum.
Native type 0x06 signatures Supported by the architecture; optional under current policy Requires Talero-specific tooling; confirm live capability before use.
ML-DSA-65 EVM verifier Experimental A verifier result does not change a classic account’s signature scheme.
Post-quantum P2P transport Active on the observed node transport Node-to-node property, not wallet-account protection.
PoQ certification Advisory Non-consensus and non-blocking.
Strict BFT finality Scheduled at height 115200; not active before that height Current bootstrap_lag output is not payout-grade finality.
PoW pool mining Active through authenticated Stratum TLS Requires a wallet-signed delegation and an independent mining key.
Miner dashboard Available after wallet-ownership authentication Individual hashrate, shares and activity remain private.
Explorer indexed reads Public with privacy and freshness metadata Indexer state can lag the node.
Selective disclosure Experimental Do not infer canonical-state membership unless the proof explicitly provides it.
Validator lifecycle Restricted workflow Not a public administration RPC surface.

How to use this guide

Check the page dedicated to the capability, then verify live runtime state. Treat policy-denied methods as unavailable and do not fall back to an internal or administrative endpoint. For mining, use the Pool and Wallet user flows rather than node work methods directly.

How to interpret runtime signals