The short answer
Match three things before sending: asset identifier, blockchain and the recipient's deposit instructions.
TRC20 · Bandwidth and Energy
Check USDT on TRONA compatibility guide. Not a transfer.
A ticker is a label, not proof of identity
For an EVM network, compare the contract address with the issuer's mainnet list. For Solana, compare the mint address. Do not rely on a wallet's imported name or logo: another token can reuse them.
Issuer listings establish token identity within their scope. They do not establish that an exchange, mixer, bridge or wallet is endorsed, solvent or able to recover an incorrect deposit.
Compatibility has three separate checks
| Check | Look for | Stop if |
|---|---|---|
| Token | Issuer-listed identifier or clearly identified representation | Only a ticker or logo is provided. |
| Chain | The recipient's exact network selection | You are inferring support from a similar address. |
| Deposit conditions | Minimum, required memo if applicable, and current availability | Deposits are suspended or the instructions conflict. |
Changing networks is a separate operation
Sending a token on one chain does not make it appear on another. A crosschain mechanism introduces its own supported routes, processing stages and dependencies. Circle's CCTP is one example: it burns and mints native USDC across supported networks.
Neither a network change nor a token conversion promises anonymity. Keep issuer controls, public records and recipient acceptance in view.
Network and token checks for the current scope
| Asset / network | Identity reference | Before relying on a route |
|---|---|---|
| USDT on TRON / TRC20 | Tether-listed identifier | Match the receiving platform's exact network and token instructions. |
| USDT on Ethereum / ERC20 | Tether-listed identifier | Budget ETH gas and confirm the recipient credits Ethereum USDT. |
| USDT on BNB Smart Chain, Polygon, Arbitrum, Optimism or Solana | Representation requires a separate check | Do not infer native Tether support from a ticker, exchange page or service label. |
| USDC on Base, Ethereum, Polygon PoS, Arbitrum, Solana or Avalanche | Circle-listed native identifiers where documented | Match the native or bridged representation and recipient policy. |
| USDC on Optimism or Algorand | Network-specific identifier and asset model | Check native/bridged or ASA rules, opt-in requirements and recipient acceptance. |
| USDT on TON | Jetton master and wallet model | The token master is not the user's Jetton wallet or a deposit address. |
Pause when the recipient's token requirements are unclear
An issuer-listed token does not establish that a particular platform accepts it. Before sending, match the exact network and contract, mint or asset identifier with the recipient's current deposit instructions. If the representation or receiving requirements are unclear, do not infer support from a ticker or logo.
Ask the recipient which token version it credits and what happens to an unsupported deposit. Keep those answers separate from fee estimates and privacy claims; none of them substitutes for confirmed compatibility.
Map each step of a multi-chain route
For a multi-chain transfer, record the input asset and chain, the operation, the exact output token and the recipient's requirements. One supported route does not establish support for every asset-and-network combination.
A single interface can involve a swap, bridge, custody transfer or several network transactions. Check the exceptions and recovery process at each step. StableMatrix does not maintain a live route catalogue; an automated label does not establish instant or guaranteed completion.
| Field | Record | Do not infer |
|---|---|---|
| Input | USDT/USDC, exact identifier and source chain. | That a ticker covers every representation. |
| Operation | Transfer, swap, bridge or custodial handoff. | That one screen means one atomic operation. |
| Output | Exact token, chain and recipient crediting rule. | That the recipient converts unsupported assets automatically. |
| Automation | Start/end events, exceptions and recovery terms. | That automated means instant, private or reliable. |
Source notes
Each reference has its own last-check date. That is not its publication date. Follow the live document for current terms and identifiers.
- CircleUSDC contract addressesIssuer-listed mainnet identifiers. A token listing is not a service endorsement. Document date not recorded. Checked: 2026-09-21.
- TetherSupported protocols and integration guidelinesExact issuer-listed asset/network combinations, including discontinued protocols. Document date not recorded. Checked: 2026-09-21.
- Solana documentationTokens on SolanaMint accounts and token accounts; why an EVM token-address model does not transfer unchanged. Document date not recorded. Checked: 2026-09-20.
- CircleCross-Chain Transfer ProtocolUSDC burn-and-mint transfers across supported networks; not an anonymity mechanism. Document date not recorded. Checked: 2026-09-20.
- CircleUSDC TermsRedemption conditions, blocked addresses, third-party platform boundaries and transfer risks. Document date not recorded. Checked: 2026-09-20.
- TetherToken terms and risk disclosuresIssuer rights, redemption conditions, restrictions, and third-party wrapped-token risks. Document date: 2026-02-26. Checked: 2026-09-20.
- TON documentationJetton processing guidelinesJetton master contracts, wallet contracts and transfer processing; a token master is not a user's deposit wallet. Document date not recorded. Checked: 2026-09-21.
- Algorand documentationAlgorand assetsASA identifiers, opt-in and account requirements. Asset identity does not establish a third-party service route. Document date not recorded. Checked: 2026-09-21.