The ticker is only part of the asset’s identity. Match the sending network, token representation and receiving instructions before a transfer. A service advertising “multi-chain” does not establish that it accepts every token on every chain—or that it converts between chains.
Check the token against its issuer’s record and the receiving platform’s instructions. This reference is not exhaustive, and inclusion here does not mean a service accepts the token.
11 of 11 network entries
Compare the token contract with the issuer’s entry for Ethereum; distinguish a different token that reuses the ticker.
Fee check: ETH for Ethereum gas
Receiving instructionsEthereum and the exact token contract must both be accepted.
Match TRC20 USDT against the issuer’s TRON entry. Do not infer USDC support from USDT support.
Fee check: Bandwidth / Energy; TRX when applicable
Receiving instructionsConfirm TRON token support and the recipient’s credit conditions.
Check the token contract and issuer or bridge. A BEP20 label does not by itself establish issuer-native USDT or USDC.
Fee check: Check the wallet’s BNB gas requirement
Receiving instructionsConfirm the specific representation, not just the stablecoin ticker.
Compare the token mint with the issuer’s Solana record and check wallet support for that token.
Fee check: Check SOL and account-related costs
Receiving instructionsConfirm the intended mint and destination’s deposit instructions.
Use the issuer’s TON record for USDT and compare the jetton identity. A TON icon or bot is not issuer confirmation.
Fee check: Check TON fees in the sending wallet
Receiving instructionsCheck whether the recipient requires a comment or memo as well as an address.
Compare the numeric asset ID with Circle’s Algorand entry. A ticker or asset name alone is not sufficient.
Fee check: Check ALGO fees and account requirements
Receiving instructionsConfirm acceptance of that asset ID and the receiving account’s requirements.
Circle issues native USDC on Base. USDbC denotes USDC bridged from Ethereum and is not Circle-issued. Match the contracts separately; establish the issuer or bridge for any USDT token too.
Fee check: Check the wallet’s Base fee estimate
Receiving instructionsA recipient accepting native USDC may reject USDbC. Pause unless it confirms your exact token and Base, not Ethereum, as the receiving network.
Use Circle’s Arbitrum entry for USDC and compare the exact contract. For USDT, identify that contract’s issuer or bridge separately; USDC support on Arbitrum does not establish USDT acceptance.
Fee check: Check the wallet’s Arbitrum fee estimate
Receiving instructionsConfirm the named Arbitrum network and token contract. Pause if the recipient names only a ticker or accepts a different native or bridged representation.
Match native USDC to Circle’s Polygon PoS contract; bridged USDC.e is a different token. For USDT, identify the exact contract and its issuer or bridge.
Fee check: POL replaced MATIC as Polygon PoS’s gas token. A USDT or USDC balance alone does not cover gas.
Receiving instructionsPause if the recipient does not name Polygon PoS and the accepted token, or accepts native USDC while you hold USDC.e.
Compare USDC with Circle’s Avalanche C-Chain contract. USDC.e is a bridged representation, not native USDC. Verify the issuer or bridge for a USDT contract separately.
Fee check: Reserve AVAX on C-Chain for gas; a USDT or USDC balance is not the fee asset.
Receiving instructionsStop if the receiving instructions say only “Avalanche” without confirming C-Chain. X-Chain and P-Chain are different chains.
Compare USDC with Circle’s OP Mainnet contract, not another OP Stack chain’s address. A bridged version or a USDT-labelled token needs its own issuer or bridge check.
Fee check: ETH covers execution, L1 data and any configured operator fee. Review the full wallet estimate, not just execution gas.
Receiving instructionsPause if the destination lists Ethereum or a different OP Stack network instead of OP Mainnet, or cannot confirm your token contract.
This reference is not exhaustive. Clear the filter to see the entries, or check the issuer and receiving platform directly.
Identity references: Tether protocols (opens in a new tab) and Circle USDC addresses (opens in a new tab). Recheck current records rather than relying on a ticker or icon.
Multi-chain support can mean separate deposit choices on several networks. A cross-chain route adds a conversion, bridge or other process between the source and destination. Ask the operator which meaning it intends; one does not prove the other.
Record both ends: source asset + network + token identifier, then destination asset + network + token identifier. Between them, identify who holds funds, whether the representation changes, which fees are separate and what happens if the second leg fails. Sending to a familiar-looking address does not choose or execute a bridge for you.
ERC20, TRC20 and BEP20 identify network environments or token conventions. They do not tell you whether a mixer or exchange requires KYC, keeps logs, supports a tumbler route or can make a transfer anonymous. Those are separate claims about an operator, its records and the rules that apply to the transaction.
Use this page to match the token and receiving network. For a USDT or USDC-specific mixer claim, use the relevant asset guide; for anonymous or no-logs language, model what a public observer and the operator can still see; for KYC or legal questions, read the risk guide. None of these links proves that a provider supports a route.
Start with the receiving platform’s current deposit instructions. Compare its asset, network and token identifier with your wallet. If a destination tag, memo or comment is required, treat it as part of the instructions—not an optional message.
Then check the fee asset and any minimum, confirmation or account requirement. A wallet balance in USDT or USDC does not necessarily pay native network fees. If a receiving page only names a ticker, ask the operator for the missing detail before sending.
If you already sent on a different network, keep the transaction record and contact the recipient through its official support channel. Recovery depends on the destination’s control and policy; it is not guaranteed. Do not pay an unsolicited “recovery” contact or reveal your keys.
No. It is an identity-check reference, not a provider’s supported-assets list. Issuer documentation can identify a token; only the intended recipient can confirm that its service accepts that token on that network at the time you use it.
Compare the USD₮ jetton identity with Tether’s current TON documentation, then read the recipient’s TON deposit instructions, including any required comment or memo. A search for a TON USDT mixer does not establish that a particular operator supports the route.
Compare the asset ID with Circle’s current Algorand record, then check the destination’s support and account requirements. Do not substitute an asset with a matching display name, and do not infer that a service supports Algorand because it accepts USDC elsewhere.
Changing networks is not, by itself, a privacy guarantee. The source transaction, bridge or conversion activity, destination transaction and service records may create separate evidence. Evaluate privacy claims independently from whether the transfer route is technically supported.
Technical references explain the token or network. They do not authenticate a provider or promise a result.
Issuer token identifiers and network entries; not a list of networks accepted by a particular service.
Issuer-native USDC identifiers, including chain-specific address and asset formats.
How Ethereum charges for execution, separately from an external service fee.
Bandwidth, Energy and fee-resource rules on TRON; not a provider quote.
The difference between Circle-issued USDC and USDbC bridged from Ethereum. Check the recipient’s current acceptance rules separately.
POL’s role as the native gas token replacing MATIC; not a quoted transfer cost or service-availability check.
The separate roles of C-Chain, X-Chain and P-Chain, and AVAX as the native fee asset.
Execution, L1 data and operator fees. Use the current wallet estimate; these rules do not establish a provider’s charges.