Skip to content
Tenzro
Documentation menu
Keys and identity

Wallet

One native TNZO balance with EVM, SVM and DAML views, stablecoin balances, and addresses on other networks derived from the same hardware-rooted key.

A Tenzro wallet is a smart account controlled by your hardware-rooted keys: passkeys for a person, a TPM 2.0 or Secure Enclave key for a machine. It holds one native TNZO balance, your stablecoin balances, and addresses on other networks derived from the same key. Create one in the console; see Console and passkey wallet.

One TNZO balance, three views

TNZO has one native balance per account. The EVM, SVM and DAML runtimes do not hold separate copies that need bridging or wrapping between them; each is a view of the same balance.

ViewWhat applications see
NativeThe account's TNZO balance, 18 decimals
EVMThe same balance as an ERC-20 view, readable with eth_getBalance and standard tooling
SVMThe same balance as an SPL token view for Solana-style programs
DAMLThe same balance as a holding for DAML contracts

A transfer in any runtime moves the one balance, and every view reflects it at once. Read all views in a single call:

bash
curl -s https://rpc.tenzro.xyz \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tenzro_getTokenBalance","params":{"address":"0xYourAccount"}}'
json
{
  "address": "0xYourAccount",
  "native":       { "balance_wei": "...", "decimals": 18 },
  "evm_wtnzo":    { "balance_wei": "...", "decimals": 18 },
  "svm_wtnzo":    { "balance_base_units": "...", "decimals": 9 },
  "daml_holding": { "amount_wei": "...", "decimals": 18 }
}

See Multi-VM runtime for how the runtimes share state.

Stablecoins

The wallet holds stablecoins alongside TNZO, and you can use them to pay for inference, compute and storage, and to pay gas. Stablecoin wallets are provided through Bridge.xyz. Agents pay in stablecoins over x402 and MPP. See Stablecoin payments and Payments.

bash
# All balances for an account
tenzro wallet balance --address 0xYourAccount --detailed

# Send TNZO or a stablecoin
tenzro wallet send 0xRecipient 25 --asset USDC

Sending moves money, so it needs a signature from the paying account: a passkey ceremony in the console, or a hardware-rooted signer in the CLI and SDK.

Addresses on other networks

Your key gives you addresses on other networks without any new key material:

  • EVM networks. One address, the same on every EVM network.
  • SVM networks. The Solana-format encoding of the account key.
  • Canton. A party allocated for your identity on a Canton participant, since a Canton party is not derived from a key.

Every derived address inherits the custody of the key it comes from: the same hardware roots, the same linked devices, the same guardians. There is nothing extra to back up. A wallet shows an external address as a deposit target only when it can also spend from it. Movement between networks goes through the bridges.

Reading an account

MethodAccessReturns
tenzro_getBalance, eth_getBalanceopenNative TNZO balance in wei
tenzro_getTokenBalanceopenTNZO in every runtime view
tenzro_getNonce, eth_getTransactionCountopenNext nonce
tenzro_getSmartAccountopenDeployment state and installed validator modules
tenzro_getPriceopenThe network oracle price for a token, used to value a portfolio
eth_getTransactionReceiptopenReceipt for a transaction

Priced portfolios read USD values from the network's own oracle, so the figures match what the network settles against.

Transactions

A transaction goes through Created, Pending, Confirmed and then Finalized, or ends as Failed or Dropped. Nonces are per address and sequential, which gives replay protection. Every transaction carries a hybrid signature (classical plus ML-DSA-65) whose post-quantum key is bound to the sending account; see Cryptography.

Canton holdings

Where an RPC operator runs a Canton participant, the wallet can show Canton Coin holdings for a party the operator has allocated to you. tenzro_canton_health reports whether Canton is available on a node; holdings are then read with your API key in the X-Tenzro-Api-Key header. See Canton and API keys.