Talero Documentation
Wallet

Control your account, mining key and pool access separately.

The Talero Wallet supports local ECDSA accounts, a runtime-gated native ML-DSA-65 path, and a safe hand-off from a payment address to authenticated pool mining.

Local account backup Runtime-gated signing Separate mining key Pool ownership proof

Back up local accounts before deleting a local copy. Never give a miner the private key of the address that receives payouts.

Local accounts and transaction routes

Accounts marked Local backup can sign in the browser. Keep an offline backup and verify the address before receiving funds. The classic route uses ECDSA secp256k1 and Ethereum-compatible tooling. The native type 0x06 route uses ML-DSA-65, but its availability is determined at runtime: the current public-testnet policy permits classic transactions and does not make the PQ route mandatory.

Capability, privacy, safe-mode and write-governance decisions are enforced by the deployed services. A visible feature is not a promise that the corresponding write is currently enabled.

Configure mining without exposing the payout key

  1. On Wallets, choose a local payment account and select Configurer le minage.
  2. The wizard loads the active pool profile and creates an independent random mining key locally. It does not derive that key from the payment account.
  3. Review and sign the exact EIP-191 delegation with the payment account.
  4. Download mining.key and mining-delegation.json, protect both files with owner-only permissions, and install them only on the miner.
  5. Renew the delegation before it expires. The wallet does not retain the generated mining key.

The payment private key must never be copied into mining software. The downloaded mining key authorizes a mining identity; payouts remain bound to the delegated payment address.

Activate the private pool dashboard

Select Activer sur la pool beside the mining/payment address. The wallet obtains a short-lived, single-use challenge from the pool, signs its exact text locally, verifies the recovered address, then sends only the address, challenge identifier and signature to the pool. No blockchain transaction is created and no TLRO is spent.

After verification, the pool establishes a private dashboard session for that address. This ownership proof is separate from the mining delegation: one authorizes pool work and payout binding, the other unlocks address-specific statistics.

Finality and privacy

Treat a bootstrap_lag finalized-head response as policy lag, not irreversible BFT settlement. Address balances or activity can also be masked by privacy policy. The wallet must display these states explicitly instead of converting missing or advisory data into a success claim.

Public API boundary

The unauthenticated configuration endpoint publishes a relative RPC proxy path and non-secret network parameters. Runtime capabilities and diagnostic packs require an authenticated wallet session. The public write-governance status is deliberately reduced to a coarse enabled/disabled state; change history, actors, reasons and operator controls are not public discovery surfaces.