I Sent USDC to the Wrong Address or Network — Now What?

Take a breath — the most common version of this mistake is fully recoverable, and the second most common is usually recoverable for a fee. This page sorts every case by what can actually be done, tells you plainly when funds are gone, and warns you about the industry that preys on people in exactly your position. Work down the cases; yours is here.

First, which case are you in?

Find the row that matches. It decides everything that follows.

Case 1 — right address, wrong network: you're fine

This is the one people panic about most and it's the least serious. EVM chains share the address format, and your wallet's address is the same on Arc, Base, Ethereum, Arbitrum and the rest. If you sent USDC "to Arc" but selected Base, the USDC is at your address on Base. Add that network to your wallet (how — same steps, different parameters) and it appears. Then bridge it to where you wanted it (CCTP to Arc). Total cost: a bridge fee and some minutes. The trap inside this case: if the "wrong network" is one your wallet can't be configured for — a non-EVM chain like Solana — the address format differs and the transaction would normally have failed rather than landed; if it did land somewhere, you're in a different case.

Case 2 — exchange deposit address, unsupported network: ask, pay, wait

Exchange deposit addresses belong to the exchange's wallets, so funds sent on a network they don't support for that asset sit in a wallet the exchange controls but isn't watching. Most large exchanges have recovery processes, with published fees and no guarantee. As of September 2026: Coinbase offers self-serve recovery for certain assets on eligible networks, free up to $100 and 5% of the amount above $100, plus network fees. Binance quotes roughly 30 working days and a 20 USDT fee for unsupported-network deposits, with explicit categories it won't recover. Kraken lists $200 for an unsupported token on a supported network and $500 for an unlisted asset on an unsupported network, "if possible." Open a support ticket with the transaction hash, the network, and the amount; be patient and polite; and never pay anyone outside the exchange's own ticket system to "expedite" it. Sending to an exchange on Arc specifically is the launch-window version of this case — if your exchange doesn't yet support Arc deposits (Coinbase, Binance, Kraken status pages), you're asking them to recover from a chain they may not yet have tooling for, which lengthens the odds. Don't test it.

Case 3 — wrong recipient: only they can help

If you sent to a valid address that isn't yours — a typo, a lookalike address from a poisoning attack, a scammer's address — the funds belong, cryptographically, to whoever holds that key. No exchange, issuer, or developer can reverse it; Arc's sub-second deterministic finality means there is no pending window to cancel in (why). If the address belongs to a known entity (an exchange's hot wallet, a project treasury), contact them — returns do happen. If it's a scammer, the funds are gone, and the useful actions are reporting (Chainabuse, your local police, the FBI's IC3 in the US) and protecting yourself from the follow-up: recovery scammers buy victim lists and will find you. Stablecoin issuers can freeze addresses on court order or in narrow circumstances, but that is not a consumer recovery channel, and Circle's freeze policy is deliberately restrictive.

Case 4 — sent to a contract: usually gone

Tokens sent directly to a smart contract's address — a token contract, a DEX pool, a lock contract — arrive at an address no person controls. Unless the contract's authors built a rescue function (some did; most didn't), nothing can move them out. Check the contract on Arcscan (reading a contract) for anything named like rescue or sweep, and contact the project; then, honestly, move on. The prevention is the whole lesson: test transactions first, and never paste a contract address where a wallet address belongs.

What about the "recovery services" offering to help?

They are the second scam. Firms and individuals who promise to recover lost or stolen crypto for an upfront fee — often posing as law firms, "blockchain forensics experts," or even government agencies — took $1.4 billion from 10,516 US victims in 2025 according to the FBI, which has issued specific warnings about fictitious law firms targeting people who've already lost funds. The tells are universal: upfront payment, guaranteed results, contact only via Telegram or webmail, and unsolicited outreach after you posted about your loss. Legitimate paths — exchange tickets, law enforcement, blockchain-analytics firms working with police — never guarantee and never charge you first. If your loss came from a compromised wallet rather than a mistaken send, the triage guide covers the different, urgent sequence.

FAQ

I sent USDC to my Arc address but on Ethereum. Is it lost? No. Your address is the same on Ethereum; add Ethereum to your wallet, the USDC is there, and you can bridge it to Arc via CCTP.

Can Circle reverse a USDC transfer? No. Transfers are final; Circle can freeze addresses only in narrow legal circumstances, which isn't a consumer recovery mechanism.

How long does exchange recovery take? Weeks is typical — Binance quotes about 30 working days for unsupported-network cases. Fees range from a percentage (Coinbase) to flat amounts (Kraken: $200–$500). Nothing is guaranteed.

Someone is offering to recover my funds for a fee. Legit? Almost certainly not. Upfront fees plus guaranteed recovery is the recovery-scam signature; the FBI logged $1.4B in such losses in 2025.

How do I stop this happening again? Send a small test amount first (cents on Arc), never copy addresses from transaction history, match the network to the destination every time, and use an address book.