Sent Crypto to the Wrong Network? What Can Be Recovered and How

1. Is crypto sent to the wrong network lost?

Not usually. The coins are not floating anywhere: a confirmed transaction moved them to the destination address on the network you selected, and they stay there. What "wrong network" means in practice is that the address you pasted was meant for a different ledger, so the owner of the address is not looking at the one where the coins arrived.

Whether you can get them back depends on who holds the key to that address and on which network the coins landed. MetaMask's support page draws the line clearly: your Secret Recovery Phrase "generates the same address across all EVM-compatible networks", so tokens sent on the wrong EVM network are reachable by switching network, while "if you sent tokens to an address on a non-EVM network, it's likely your tokens are gone forever".

Exchanges are the middle case. The deposit address belongs to the exchange, so only the exchange can move what arrived there, and each one has a written policy for it: Kraken and Binance publish recovery tables with fees and waiting times, Coinbase runs a self-service tool for eligible assets, Binance.US a deposit recovery tool for supported ones. None of them reverses the transaction, and none of them promises success.

2. First, find out where the coins actually are

Copy the transaction hash from the sending wallet or exchange and open it on the explorer of the network you selected when sending: Etherscan for Ethereum, BscScan for BNB Smart Chain, Polygonscan for Polygon, Arbiscan for Arbitrum One. The transaction hash guide shows where to find the hash and how to read the page.

Three fields matter. The status: if it says failed or pending, nothing moved and there is nothing to recover. The recipient address: that is where the coins are, and it tells you whether a wallet you control, an exchange or a stranger holds the key. The token: a USDT transfer on BNB Smart Chain is a BEP20 token transfer, which is a different contract from USDT on Ethereum, so the recipient has to look for that contract on that chain.

If you are not sure which network the label on the form referred to, the network names guide maps ERC20, BEP20, TRC20, Arbitrum One, OP Mainnet and the other labels to their chains and chain IDs.

3. Case 1: the coins are in your own wallet, on the wrong EVM network

This is the recoverable case, and you do not need anyone's help. An EVM address is derived from your key, so the address that received the coins on BNB Smart Chain is the same address your wallet shows on Ethereum. Binance Academy's recovery guide lists the steps for a wallet that already supports both chains: switch to the network the coins are on, and "the tokens should appear"; then send them back to the exchange through the matching deposit network, or move them with a bridge.

If the wallet shows the network but not the token, add the token with its contract address on that chain; MetaMask notes that "the recipient may need to add the token manually". If the wallet does not offer the network at all, add it: Binance Academy's example is BNB Smart Chain with chain ID 56, the BNB symbol and the BscScan explorer, and for a wallet that cannot add networks the guide's answer is to import the private key into one that can, such as MetaMask.

The step people forget is gas. Moving the coins off that chain costs a fee in the chain's own coin: BNB on BNB Smart Chain, POL on Polygon, ETH on Arbitrum, Base and OP Mainnet, AVAX on Avalanche. Binance Academy's guide says to hold a small amount of BNB for the BSC fee before sending the tokens back. The EVM wallet address guide explains why the address repeats across chains, and this is what a plain transfer costs on each of them right now:

Gas you will need on the chain where the coins landed

Live figures for November 7, 2026 at Normal speed on the ChainGate gas tracker. A token transfer costs more than a native transfer; a bridge costs more again.

The EVM chain ID list has the chain ID, native token and explorer for every network you may need to add.

4. Case 2: the coins went to a non-EVM network or an address of another format

Here the shared-address trick does not work. Bitcoin, Bitcoin Cash, Solana, Tron and the XRP Ledger derive addresses differently, so the address that received the coins on one of them is not an address your wallet controls on another, and in most cases it is not an address anyone controls.

Exchanges spell out the outcomes. Kraken's list of unsupported deposits marks Bitcoin Cash sent to a Bitcoin address, DOT sent to a KSM address and the reverse, and tokens from Fuse, Harmony, Fantom, xDAI or Avalanche sent to its Ethereum address as cases where the funds are lost, and says deposits made through privacy tools such as CoinJoin or PrivateSend will not be credited and may be lost. MetaMask's wording for the self-custody side is that the tokens are "likely gone forever".

The exceptions are narrow: a wallet app that supports both chains and derived the receiving address from the same key, or a platform that holds the key for the destination address and agrees to help. If neither applies, treat the coins as gone and do not pay anyone who claims otherwise.

5. Case 3: you deposited into an exchange on the wrong network

The exchange holds the key, so recovery is its decision and its labour. The large exchanges have turned the most common mistakes into a process with a form and a price list, every one of them says recovery is not guaranteed, and deposits on networks the exchange does not support at all are the hardest case or impossible.

Kraken states that "not all cryptocurrency deposits sent to an incorrect location can be recovered", gives the example of an asset sent via Binance Smart Chain when it only supports Ethereum mainnet as one of the hardest cases, and publishes a table: a deposit that was simply not credited is recovered free, a missing or incorrect tag or memo and a deposit to a hot wallet cost the network fee, unsupported tokens on supported networks cost 200 USD, and unlisted assets on unsupported networks cost 500 USD. Its funding FAQ adds that deposits sent on unsupported networks are likely non-recoverable.

Binance runs a self-service recovery form for crypto deposited into your own account whose transaction is confirmed on the blockchain. Its table, updated in May 2026, lists a deposit not credited at no charge in 5 working days, a wrong or missing memo at the network withdrawal fee in 7 working days, old or delisted tokens at the network fee in 5 working days, smart retrieval of eligible unlisted tokens at 1 USDT in 7 working days, and unlisted tokens on supported networks, listed or unlisted tokens on unsupported EVM networks and the BNB Pioneer Burn programme at 20 USDT in 30 working days. The processing fee is charged only after a successful retrieval, and the page says fees may change and recovery is not guaranteed.

Two Binance pages set expectations lower. The incorrect-deposit FAQ says "Binance generally does not offer a token/coin recovery service" and that help is at its discretion, and the Academy guide says that "if you deposit funds to your Binance account using an incorrect network, Binance is not able to retrieve those tokens". The self-service table is the newer and more specific document; use it as the reference and expect the discretion clause to apply.

Coinbase has an asset recovery tool for unsupported assets sent to a Coinbase address: only certain assets and networks are eligible, recoveries above 100 dollars pay a 5% fee on the amount over 100 dollars plus network fees in ETH, and the recovered funds go to a self-custodial wallet you connect. For funds sent or received on an incorrect network, Coinbase's help pages state that it does not have the ability to recover them. It also credits some assets that were sent before a network was supported, once the network is added: the automatic return page gives ETH, MATIC and USDC on Polygon and DAI, ETH and WBTC on Optimism as past examples.

Binance.US offers a deposit recovery tool for supported crypto that was not credited because of a wrong address, a missing memo or a network issue, and says it "is unable to recover/return deposits of unsupported assets or deposits sent using unsupported networks".

6. Case 4: you withdrew from an exchange to the wrong network

The exchange signed a valid transaction on the network you selected and cannot take it back. Binance's self-service form excludes withdrawals explicitly, and Binance.US says withdrawals cannot be recovered. What happens next depends on the destination.

If the destination is a wallet you control, you are in Case 1 or Case 2. If it is a deposit address at another exchange, that exchange's recovery process applies: Case 3, with the receiving exchange. If it is an address you do not control, only its owner can send the coins back; Binance's incorrect-deposit FAQ puts it plainly: "if you sent your tokens to an incorrect address that doesn't belong to Binance", it cannot help, and you can only try the owner of the address or the platform it belongs to. The withdrawal address guide covers the checks that prevent this before the withdrawal is sent.

7. Case 5: right network, missing memo or destination tag

On the XRP Ledger, TON and similar networks the exchange identifies your account by a memo or tag next to a shared address, so a deposit without it arrives at the exchange but is not credited to anyone. This is the most routine recovery: Kraken charges the network fee for a missing or incorrect tag or memo, Binance charges the network withdrawal fee and quotes 7 working days, and Binance.US includes a missing memo among the cases its deposit recovery tool handles.

Binance's form asks you to apply only if the funds have still not arrived one hour after the transaction, and to provide the tag or memo when it is required for the refund. Keep the transaction hash: all three exchanges identify the deposit by it.

8. What nobody can recover

Some losses are final, and recognising them early saves money and time:

A 0x address on a non-EVM network, or a format mismatch

Bitcoin Cash sent to a Bitcoin address, tokens sent to an address that only exists on another chain family, Solana or Tron coins aimed at an EVM address. Kraken lists these as lost; MetaMask calls them likely gone forever.

Coins sent to a contract that cannot handle them

MetaMask warns that there is no guarantee of recovery when tokens go to a smart contract address, because the contract may not be programmed to receive them; Binance's self-service form excludes deposits whose address is a contract outside its BNB Pioneer Burn programme.

An address nobody controls

A typo that still passes the format check, or a burn address. No exchange can move coins from an address it does not hold the key to, and no wallet vendor can either.

A reversed transaction

Blockchains do not reverse confirmed transactions. Every recovery above is a new transaction sent by whoever controls the receiving address.

Recovery services that contact you

Binance.US warns to "be cautious of groups or individuals claiming they can recover lost funds for a fee", and MetaMask says it will never message you first or ask for your Secret Recovery Phrase. Anyone asking for your seed phrase to recover funds is taking the rest.

9. How much does recovery cost and how long does it take?

The published figures, as of November 2026. Both exchanges say the fees may change and that the waiting times start once they have the information and the fee:

For a self-custody wallet the cost is the gas of the transactions you send yourself, which the live table in Case 1 shows per network, plus a bridge fee if you bridge.

10. How to write the recovery request

Exchanges identify the deposit by its transaction hash, so the request is mostly data. Kraken asks for the transaction ID, the cryptocurrency and amount, the deposit address you used and the date and time, and may ask for screenshots or correspondence. Binance's form starts from the hash: paste it, and if the transaction is in its system the coin, network, deposit address and amount are filled in; otherwise you enter them. Binance may then ask for a video to prove the deposit is yours, and shows the status under its application records.

Three habits make the request go through. Copy the hash from the explorer instead of typing it. Wait for the status the exchange asks for: Binance wants the transaction confirmed on chain and at least one hour old. And send it only through the support channel inside your account; nobody from an exchange will contact you first about a lost deposit, and nobody legitimate needs your seed phrase to process it.

11. How to avoid it next time

The rule is the one Binance's withdrawal guide states: make sure the selected network is the same as the network of the platform you are withdrawing to, because sending on the wrong network "will result in permanent loss". In practice that means reading the destination's deposit page first (Kraken, for example, publishes the exact networks it accepts for each stablecoin), picking that network on the sending side, and sending a small test amount to a new address or network. The withdrawal address guide walks through the form field by field.

If you build withdrawal flows, validate the address for the network it will be sent on and store the chain ID with it, because the address alone cannot tell networks apart:

import { ChainGate } from 'chaingate';

const cg = new ChainGate({ apiKey: process.env.CHAINGATE_API_KEY });

// One 0x address is valid on every EVM network; only the chain ID says where the coins went
const address = '0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045';

cg.networks.ethereum.isValidAddress(address); // true (Ethereum, chain ID 1)

const bnbSmartChain = cg.networks.evmRpc({
  rpcUrl: 'https://bsc-dataseed.binance.org',
  chainId: 56,
  name: 'BNB Smart Chain',
  symbol: 'BNB',
});
bnbSmartChain.isValidAddress(address);        // true (same string, chain ID 56)

// A Bitcoin check rejects it, and a Bitcoin address fails on every EVM network:
// the format check is the last thing that stops a cross-family mistake
cg.networks.bitcoin.isValidAddress(address);  // false
cg.networks.ethereum.isValidAddress('bc1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4'); // false

// Store the chain ID next to the address: 56 and 1 share the string, not the ledger
const withdrawal = { address, chainId: 56 };

The address validation documentation lists the networks the SDK knows by name and how to register the rest by chain ID.

12. Where to go from here

If the coins are reachable, the EVM chain ID list gives you the network details to add, the contract address guide shows how to find the token's contract on that chain, and the gas tracker tells you what moving them will cost. The network names guide decodes the labels that caused the mistake. If you are building a platform that validates addresses per network and sends on Bitcoin, Ethereum and the other EVM chains from one SDK, ChainGate does that.

Frequently asked questions