You meant to send USDC to your wallet on Base. Somewhere along the way, the wrong network got selected, on an exchange withdrawal screen or inside another wallet, and the tokens left on a different chain instead. The transaction confirmed. The address in the confirmation looks correct. But your balance on Base has not moved.
This is one of the most common mistakes in crypto, and it causes a specific kind of panic because there is no support line to call and no undo button. The good news is that the outcome depends entirely on two details: who controls the destination address, and whether the network you sent to is one your wallet can actually reach. Understanding those two details tells you, calmly, whether your funds are recoverable.
Why This Mistake Happens So Easily
Base, Ethereum, and most other EVM-compatible networks (Arbitrum, Optimism, Polygon, and others) share the same address format. A wallet address is not tied to a single chain the way a bank account number is tied to a single bank. It is derived from a key pair, and that same key pair produces a valid, working address on every EVM chain at once.
That is convenient almost all the time. It means you do not need a different address for every network your self-custody wallet supports. But it also means a wallet interface, exchange withdrawal form, or block explorer will accept a Base address without complaint, even if you have accidentally chosen Ethereum mainnet, Arbitrum, or Polygon as the network for that send. The address is valid everywhere. The tokens still only exist on the chain you actually sent them on.
The Two Scenarios That Matter
You sent to your own self-custody address, on the wrong network.
This is the good scenario. Because the same address exists on every EVM chain, your funds are not lost. They are sitting at an address you control, just on a different network than you intended. You can reach them by adding that network to your wallet and viewing the balance there. Most wallets, including browser extensions and mobile apps, let you add a custom network by entering its name, RPC endpoint, and chain ID, information you can find on a site like Chainlist.
Once the network is added, your existing recovery phrase or account unlocks the same address on that chain, and the tokens appear. From there you can either use them on that network directly, or send them back across using a bridge to get them onto Base.
You sent to a deposit address at an exchange or another custodial service, on the wrong network.
This is the harder scenario. Exchanges control the private keys behind their deposit addresses, and many only monitor specific networks for each address. If you send a token on a network the exchange does not scan for that particular deposit address, the funds arrive on-chain but the exchange's systems never register the deposit, so nothing credits to your account automatically.
Recovery here depends entirely on the exchange. Some support teams can manually locate the deposit and credit it, sometimes for a fee, sometimes after a lengthy verification process. Others state plainly that cross-network deposits cannot be recovered at all. If this happens to you, the first step is always to check the specific exchange's help center or open a support ticket with the transaction hash, rather than assume either outcome.
How to Check What Actually Happened
Before assuming the worst, confirm where the transaction actually landed.
- Find the transaction hash from your sending wallet's activity history.
- Identify the network it was sent on. If you are not sure, the transaction hash format is often shared across chains, so you may need to check a few block explorers.
- Search the hash on the matching explorer. Basescan for Base, Etherscan for Ethereum mainnet, Arbiscan for Arbitrum, and so on. Each major EVM network has its own public explorer.
- Confirm the destination address shown in the transaction matches the address you meant to send to.
If the transaction confirmed and the destination address is one you control, your funds exist and are reachable once you add the correct network to your wallet, as described above.
One Detail That Trips People Up During Recovery
Even after you locate funds sitting on the "wrong" network at your own address, moving them requires paying a network fee, and that fee has to be paid in that network's own gas token, not in the token you are trying to move. USDC sitting on Arbitrum needs a small amount of ETH on Arbitrum to pay for the transaction that sends it onward. If you have never used that network before, your balance there is zero, and you will need to acquire a small amount of that network's gas token first before you can access the funds you already have.
This is a common second stumble in recovery attempts: people find their tokens, celebrate too early, and then discover they cannot move them without funding gas on a chain they never intended to use.
How to Avoid This Going Forward
The habit that prevents this mistake is simple and worth building permanently: check the network selector every time, on every send, especially on exchange withdrawal screens where the default network is not always the one you expect. Confirm the network name matches your destination wallet before you approve anything. A few extra seconds of checking costs nothing. Recovering from a wrong-network send, even in the best case, costs time, a new network setup, and sometimes a gas token you have to buy just to get your own money moving again.
If you are ever unsure which network an address belongs to, it is safer to send a small test amount first, confirm it arrives where expected, and only then send the full amount. That habit applies to any new destination address, not just cross-network sends, and it is one of the cheapest insurance policies available in self-custody.