USDT and USDC: choose the network before the address
USDT and USDC names do not determine a network. Match the receiving service’s asset and network instructions, then verify any token identity against the issuer’s chain-specific list.
Worked example
| Question | Authoritative check | Avoid |
|---|---|---|
| Which network? | Recipient’s supported deposit network | Choosing by ticker alone |
| Which token contract? | Circle USDC or Tether protocol list | Search ad or copied token logo |
| Which destination? | Recipient’s receive screen | Issuer’s token contract |
Worked comparison
A recipient requesting USDC on Ethereum is not requesting USDC on Solana. Even when both are issuer-supported, the accounts and transfer environments differ. A bridged representation can also differ from an issuer-native token on the same network.
Why there is no contract pasted here
Issuer lists cover multiple deployments and may change. The references below take you to the issuer’s mappings; this guide does not maintain a second stablecoin contract directory. Read the exact network row and match it to the receiving instructions.
Common pitfalls
- Do not treat “ERC-20” as a universal cross-chain deposit route.
- A valid checksum cannot confirm that a service supports the asset.
Related references
Primary sources
Examples explain identifiers. They are not investment recommendations.