Supported mainnets

This reference follows the published Oath 4.0.0 (73) source and network catalog, reviewed September 28, 2026. It covers mainnets. Available tokens and import formats can vary by app release and the remote asset catalog.

Bitcoin family

  • Bitcoin — BTC
  • Bitcoin Cash — BCH
  • Litecoin — LTC
  • Dogecoin — DOGE

Bitcoin supports conventional address families including Taproot, Native SegWit, Nested SegWit and Legacy, with supported BRD recovery paths. A wrapped BTC token on another chain is a different asset. Silent Payments receiving and discovery are unavailable in the public 4.0.0 release; read the recovery limits.

Ethereum-compatible networks

The asset in parentheses is the native network-fee asset; its name does not imply that the same ticker on another chain can pay this network’s fees.

  • Ethereum (ETH)
  • BNB Smart Chain (BNB)
  • Arbitrum (ETH)
  • Base (ETH)
  • Polygon (POL)
  • Optimism (ETH)
  • Avalanche C-Chain (AVAX)
  • Gnosis (xDAI)
  • Linea (ETH)
  • Scroll (ETH)
  • Taiko (ETH)
  • Telos (TLOS)
  • X Layer (OKB)
  • Arc (USDC)

For tokens, match the network and contract address as well as the ticker. The same 0x address format is used across multiple EVM networks; that visual similarity does not transfer assets between them. Oath does not bridge a deposit to the network you intended.

Other account networks

  • Solana — SOL
  • TRON — TRX
  • TON — TON
  • Sui — SUI
  • Aptos — APT
  • NEAR — NEAR
  • Stellar — XLM
  • XRP Ledger — XRP

Network rules, account activation, reserves, memos, destination tags and transaction costs differ. Use the requirements shown by the sending or receiving service. Token support is not a promise that every token or every import format works on that network.

Before receiving a payment

  1. Choose the intended asset and network in Oath’s Receive flow.
  2. Confirm that the sender offers that exact network. An exchange’s withdrawal-network label matters.
  3. Compare the full destination on trusted devices, and include a memo or tag when the destination requires one.
  4. For a new route, verify it with a small test amount you are comfortable risking, including the network fee.
  5. Check the transaction on the correct network and keep the recovery credentials private.

The receiving guide explains addresses, QR requests and network selection. The Bitcoin guide covers address families and discovery limits.

Import and recovery are separate checks

A network appearing here does not mean every historical wallet backup is compatible. Preserve the original format, recovery phrase, optional passphrase and any required derivation information. Follow the import-method guide and verify the expected public accounts before relying on a recovered wallet.

Download the official Oath Wallet app