Sent Crypto to the Wrong Network or Address? What You Can Recover

By Merunas Grincalaitis, founder of MEV DAO and a developer who builds MEV, sniping and trading bots on Ethereum. Last updated: Nov 1, 2026.

TL;DR: If you sent crypto to the wrong network but to your own normal wallet address (an EOA like MetaMask, Rabby or Ledger), it's usually not lost: the same private key controls the same 0x address on every EVM chain, so you switch networks, add the token and bridge it back. Sends to a smart contract wallet on a chain where it isn't deployed, to an exchange on an unsupported network, or to a token contract depend on someone else's cooperation. A wrong address you don't control is almost always gone, and nobody can reverse a confirmed transaction.

I get this question a lot, usually with a screenshot of an empty balance. Most of the time the money is sitting exactly where it was sent, on a chain the person isn't looking at. Here's the triage I go through.

First, is the transaction actually confirmed?

Check the transaction hash on a block explorer before doing anything else. If it's still pending, you can still act. If it's confirmed, nothing can undo it, and the only question left is who controls the receiving address on that chain.

MetaMask's guide starts the same way. If the transaction is Pending and heading to the wrong place, cancel it with a 0 ETH self-transfer using the same nonce and a higher fee, as I explain in how to speed up or cancel a stuck Ethereum transaction. If it shows Success, open the hash on the explorer of the chain it was sent on (Etherscan, Arbiscan, Basescan, BscScan) and note three things:

  1. The chain. That's where the funds are.
  2. The recipient (for token transfers, the address in the token transfer line, not the token contract).
  3. The recipient type. Explorers label smart contracts "Contract". An address with no code is an EOA, an externally owned account controlled by a private key.

Which "wrong send" cases can you recover?

Recoverability depends on one thing: does anyone with a working key or contract control the receiving address on the chain where the funds landed?

What happened Who controls the funds? Can you get them back?
Sent to your own EOA, but on the wrong EVM chain You, with the same key Yes, switch networks and move them
Sent to someone else's EOA on the wrong EVM chain The recipient, with the same key Yes, if they cooperate
Sent to your Safe or smart wallet on a chain where it isn't deployed Nobody yet Often, if you deploy the same wallet there first
Sent to an exchange deposit address on an unsupported network or token The exchange Sometimes, through its recovery process and fees
Sent to a token or protocol contract The contract's code Only if the contract has a rescue function
Sent to a mistyped or unknown address Whoever holds that key, often nobody Almost never
Sent from an EVM chain to an address meant for a non-EVM chain Usually nobody Almost never

Sent to your own wallet on the wrong network: how do you get it back?

Switch your wallet to the network the funds landed on, add the token by its contract address, then send or bridge it where you meant it to go. For a normal wallet this works because an EVM address is derived from your private key, not from the chain.

MetaMask says your Secret Recovery Phrase generates the same address across EVM networks such as Polygon, Arbitrum, Optimism and Avalanche, so those tokens are not lost. BNB Chain's docs give the same steps:

  1. Add the network to your wallet (Rabby shows all supported chains automatically).
  2. If the token doesn't appear, import it using its contract address on that chain, copied from that chain's explorer.
  3. Get a little of that chain's gas token: ETH on Arbitrum, Base and Optimism, BNB on BNB Chain, POL on Polygon. It's the same problem as in do you need ETH to send USDT or USDC.
  4. Send the tokens where you meant to, or bridge them back with the official or a reputable bridge.

One catch: the token on the other chain may not be the asset you think. USDT on BNB Chain is a different contract from USDT on Ethereum, so check liquidity before assuming value. If the address belongs to a friend, the same applies to them: their key works on every EVM chain.

What if you sent it to a Safe or smart contract wallet on the wrong chain?

A smart contract wallet only exists on the chains where it has been deployed, so funds sent to its address on another chain sit at an address nobody controls yet. You can often fix this by deploying the same wallet to that chain at the same address, but you have to do it before someone else does.

That's what happened to Wintermute in 2022: the Optimism Foundation sent 20 million OP on Optimism to the address of Wintermute's Gnosis Safe, which only existed on Ethereum. In its post to the Optimism community, Wintermute wrote that controlling a mainnet Safe "doesn't guarantee control on other EVM compatible chains (unlike ordinary wallets)." An attacker replayed the old Safe factory deployment on Optimism and, per Inspex's analysis, deployed 10,044 Safes until one landed on that address, because the old factory used CREATE, where the address depends only on the factory and its nonce.

Modern Safes handle this better. The Safe multi-chain docs list "accidental fund transfers" as a reason to redeploy: Safes from Singleton v1.3.0 or later can be deployed at the same address, with the original owners, threshold and modules, from the Safe{Wallet} interface. Limits:

  • Safes created from v1.0.0, v1.1.1 or v1.2.0 can't be replayed this way.
  • zkSync Era isn't supported, and Safe's help center warns that funds sent there to a Safe address that isn't deployed will be lost.
  • The new Safe starts with the original owners. If one of those keys has since been compromised, don't redeploy with it.

ERC-4337 smart accounts work similarly when the same factory exists on the other chain, so ask the wallet's support before trying anything. An EOA with an EIP-7702 delegation is still an EOA whose key works everywhere; see EIP-7702 vs ERC-4337 if you're unsure which you have.

Sent to an exchange on the wrong network: can the exchange recover it?

Sometimes. Exchanges control their deposit addresses, so they technically can, and the big ones run recovery processes with fees and no guarantee. What you can't do is fix it yourself, because you don't hold the keys.

  • Coinbase runs an asset recovery tool for certain unsupported assets and networks. You enter the network, transaction ID and Coinbase address, then connect a self-custodial wallet to receive the funds. Recoveries above $100 cost 5% of the amount over $100, plus network fees, and ineligible assets just return an error.
  • Binance has a self-service recovery page for deposits with a missing memo, unlisted tokens and unsupported EVM networks. Fees vary by case, are only charged if retrieval succeeds, and can change. Binance says recovery isn't guaranteed.
  • Smaller exchanges need a support ticket with the hash, network, token and amount. A real exchange never asks for your seed phrase.

Sent tokens to a contract address: are they stuck forever?

Usually yes, unless the contract has a function that lets someone with authority move tokens out. An ERC-20 transfer to a contract doesn't fail just because the contract can't use the tokens. The balance is simply recorded under the contract's address.

MetaMask says there's no guarantee of recovery, though the project team may help. Open the contract's "Write Contract" tab on Etherscan and look for functions like rescueTokens, recoverERC20 or sweep. If one exists and is owner-only, contact the team through the official links on its site. If not, and the contract isn't upgradeable, the tokens are effectively burned. The classic version is pasting the token's own contract as the recipient: USDT sent to the USDT contract stays there.

Sent to the wrong address entirely: is there anything you can do?

If the address belongs to a stranger or to nobody, the funds are gone, and blockchains have no reversal button. The only real path is asking the owner to send it back, which works when you can identify them.

Find out how it happened first. If you copied the address from your history and it only matched in the first and last characters, that's likely address poisoning, explained in can someone steal your crypto with just your wallet address. If funds left without you sending them, it's a compromised wallet, not a wrong send: go to the wallet drained checklist.

Who can actually help, and who is a scammer?

Wallet providers, exchanges, Safe and the project behind a contract can help within their own systems. Random "recovery experts" can't reverse a blockchain transaction. MetaMask notes that it will never DM you and never ask for your Secret Recovery Phrase.

Post about a lost transfer and the replies fill with "recovery" offers for an upfront fee, some asking for your seed phrase to empty what's left. See crypto recovery scams. The one legitimate technical case is funds still in an address you control while a sweeper bot steals any gas you send. That needs a Flashbots bundle rescue, which works because you still hold the key.

How do you avoid sending to the wrong network next time?

Send a small test first, check the network on both sides, and never copy an address from your transaction history.

  1. Match the network on the withdrawal screen to the deposit screen exactly: "ERC20", "Arbitrum One" and "BEP20" are different networks.
  2. Send a test amount and wait for it to arrive.
  3. For Safes and smart accounts, confirm the wallet is deployed on the destination chain.
  4. Copy addresses from your wallet's address book and check the whole string.

Frequently asked questions

What happens if I send USDT on the wrong network?

If the recipient is a normal wallet (EOA), the USDT is on that network at the same address and the owner can switch networks to see and move it. If the recipient is an exchange that doesn't support that network, only the exchange's recovery process can return it.

Can I get my crypto back if I sent it to the wrong address?

Only if the owner of that address sends it back. Confirmed blockchain transactions can't be reversed, so if the address is unknown or nobody controls it, the funds are lost.

Is ETH on Arbitrum or Base the same address as on Ethereum?

Yes, for a normal wallet. The same private key controls the same 0x address on Ethereum, Arbitrum, Base, Optimism and other EVM chains. Smart contract wallets are different, because they only exist where they've been deployed.

Can I recover tokens sent to a smart contract?

Only if the contract has a function that lets an authorized party withdraw tokens, or if it can be upgraded. Check the contract on the block explorer and contact the project through its official channels.

Can a crypto recovery service reverse my transaction?

No. Nobody can reverse a confirmed transaction. Services that promise to, especially for an upfront fee or your seed phrase, are a common scam.

If your tokens are still in an address you control but a sweeper bot takes every bit of gas you send, that's the case we handle at MEV DAO. Here's how our token rescue service works.

← More on MEV Bot Development All articles