Recover Crypto Sent on the Wrong Network
Sent crypto on the wrong network? When EVM-to-EVM mistakes are recoverable, when cross-ecosystem sends are not, and the steps to request a recovery.
Updated June 2026 ยท Reviewed by the PipeFlare team
EVM-to-EVM mistakes can sometimes be recovered; cross-ecosystem sends usually cannot
If both chains are EVM-compatible (Ethereum, BSC, Polygon, Base, Optimism), Coinbase Asset Recovery or Binance Smart Retrieval may sweep the funds. Solana, Bitcoin, and other non-EVM sends to an EVM address are almost always permanent because the chains do not share key cryptography.
Read the official source โCategory
Wrong-network send
Recoverability
Sometimes recoverable
What you need
Transaction hash, source and destination chains, the deposit address, the token contract address, and an account on the destination exchange
Time window
Days to a few weeks โ no hard deadline, but token eligibility lists change so submit promptly
About this situation
If you sent crypto on the wrong network, recovery depends on which two networks were involved. EVM-to-EVM mistakes are sometimes recoverable. For example, USDC sent on Polygon to a Coinbase Ethereum address can often be retrieved. Cross-ecosystem mistakes, like sending Solana USDC to an Ethereum address, are almost always permanent. The chains use different cryptography, so the destination address does not exist on the receiving network. Whichever case you are in, ignore every "recovery service" that messages you after the mistake โ those are scammers, not help.
How it actually works
Every EVM chain uses the same key system and the same 0x address format. One private key controls the same address on Ethereum, Polygon, BSC, Base, and Optimism. If an exchange holds the key for your deposit address, it also controls that address on every other EVM chain. That is why exchanges can sometimes sweep wrong-network deposits and credit your account. Solana and Bitcoin use different cryptography and different address formats, so no shared key exists to recover funds across those ecosystems.
Step by step
- 1Stop sending. Confirm the transaction hash and write down the source chain, the destination chain, and the receiving address.
- 2Check the destination platform's recovery policy. Coinbase Asset Recovery covers unsupported ERC-20 tokens received on Ethereum, BSC, Polygon, Base, and Optimism. Binance Smart Retrieval covers ETH, BSC, MATIC, TRX, FTM, HT, plus OKC, KCC, and CRONOS.
- 3Submit the official recovery request inside your exchange account. Provide the transaction hash, the token contract address, both networks, and the deposit address. Never pay a third-party recovery service.
- 4Wait. Coinbase charges no fee under $100 and 5% above $100 plus a network fee. Binance offers a paid expedited track of about 14 business days. Most requests resolve in days to a few weeks.
What works in your favor
- EVM-to-EVM recoveries succeed often when the destination is a major exchange that supports the asset and network combination.
- Coinbase publishes a clear fee schedule: free under $100, 5% above $100, plus the network gas fee.
- If you control the destination wallet yourself, you can usually import the same seed phrase into a wallet that supports the other EVM chain and move the funds.
Watch out for
- Cross-ecosystem sends like Solana to Ethereum or Bitcoin to BSC are not recoverable. The address does not exist on the other chain.
- Recovery is never guaranteed. Token eligibility lists change, and exchanges reject requests for unsupported assets without appeal.
- If the deposit address belongs to a self-custody wallet you do not control, no exchange can help.
- Every third-party "recovery service" that DMs you after a wrong-network send is a scam targeting fresh victims โ never pay one.
Common questions
What counts as a wrong-network send?
A wrong-network send is when you send a token over a blockchain the receiving address or platform does not accept. The most common case is sending USDC on Polygon or BSC to a Coinbase Ethereum-only address. The token exists on both chains but as separate, non-interchangeable balances.
Why can EVM-to-EVM sends sometimes be recovered?
Every EVM chain uses the same secp256k1 cryptography and the same 0x address format. One private key controls the identical address on Ethereum, Polygon, BSC, Base, Optimism, and Arbitrum. If an exchange holds the key for your deposit address, it also controls that address on the wrong chain and can sweep the funds.
Why are Solana or Bitcoin to Ethereum sends usually lost?
Solana uses Ed25519 signatures and base58 addresses. Bitcoin uses secp256k1 with addresses starting in 1, 3, or bc1. Neither shares a key system with EVM chains. The destination address you typed does not exist on the source chain in a form anyone can sign for, so no exchange has a key that can sweep it.
What does Coinbase Asset Recovery cost?
Coinbase charges no recovery fee on amounts under $100. For amounts of $100 or more, the fee is 5% of the recovered value plus a separate network gas fee. The tool covers unsupported ERC-20 tokens received on Ethereum, BSC, Polygon, Base, and Optimism.
Can I prevent this next time with a bridge?
Yes. For USDC specifically, Circle's CCTP V2 burns USDC on the source chain and mints native USDC on the destination chain across 13+ networks, including Solana. Always send a small test amount first and confirm the receiving platform supports both the asset and the network.
Sources
Other recovery guides
Want to avoid the next mistake?
Beginner guides to wallets, gas, networks, and how transactions actually work.