Why an address must be checked with its network
Check the asset, network and receiving address together before a transfer. Matching address formats or token names do not establish that the transfer route is correct.

Why can the same address have different balances?
An address needs a network context. An ordinary EVM wallet account can use the same address on Ethereum and Base, but balances and transactions are recorded separately on each network. Changing the network displayed in a wallet does not move funds. The MetaMask network guide explains that Ethereum compatibility does not make another network Ethereum Mainnet.
USDC can have a different contract on each network
The native USDC addresses published by Circle include these separate deployments:
- Ethereum Mainnet:
0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 - Base Mainnet:
0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
These are token contract addresses, not your receiving address. Do not enter them as the recipient of a withdrawal. Other contracts can copy a token’s name and logo; compare the complete address with the issuer’s official documentation.
What should you check before a transfer or withdrawal?
- Start at the receiving side. Choose the asset and network on your wallet or exchange’s receive screen. Copy the receiving address shown there.
- Match the sending side. Select the same network and confirm that the receiver supports that asset on it. Include a memo or destination tag if the receiving screen requires one.
- Identify the address type. A receiving address accepts funds, a token contract identifies an asset, and a pool address identifies a trading pool. They are not interchangeable.
- Distinguish mainnet from testnet. For example, Base Mainnet uses chain ID 8453, while Base Sepolia uses 84532. Similar names do not mean the same network; see Base’s network details.
- Check the complete details. Review the full address, amount, fees and minimum deposit requirements. For an unfamiliar route, a small transfer that meets those requirements can confirm receipt before you continue.
Coinbase’s receive instructions likewise require a supported network and any necessary tag. Follow the requirements of the platform you actually use.
The transaction succeeded, but the token is missing. What next?
Look up the transaction hash in the explorer for the network used to send it. Check the status, recipient and token contract. If you control the receiving wallet, check which network and token it displays. If the recipient is an exchange, also check its supported deposit network, required confirmations and minimum amount. Success on the blockchain does not mean the platform has credited the deposit.
Whether a wrong-network transfer can be handled depends on address control, the asset and platform support. Recovery is not guaranteed. Provide official support with the transaction hash, never your recovery phrase or private key.
Related transfer and token guides
Continue with the exchange-to-wallet withdrawal walkthrough. If the address you found belongs to a pool, read how a new pool differs from a newly issued token.