Sent crypto to the wrong network or address: what can and cannot be recovered

First, find out where it went

Every transfer has a transaction ID, and the network it was sent on keeps a public record of where it ended up. Before anything else, look that transaction up on the network it was actually sent on — not the one you meant. If it is confirmed there, the funds exist at that address on that network, and the question becomes who controls that address. Binance’s own guidance for missing transfers leans on the same ID: a receiving platform can in most cases locate funds from it (Binance).

Case one: your own address, another network

This is the case with the best outcome. Ethereum and the networks compatible with it share one address format, so your address exists on all of them at once (MetaMask Help Center). Sent to yourself on BNB Smart Chain instead of Ethereum, the funds are simply on BNB Smart Chain, and a token sent there does not show up while the wallet is looking at Ethereum (BNB Chain). Switch the wallet to that network — adding it if needed — and they appear.

Case two: a wallet that does not support the network

If a wallet cannot show the network at all, the funds are still at an address you control; you need a different wallet to reach them. Phantom’s own guidance for tokens sent to it on networks it does not support, such as BNB Smart Chain or Arbitrum, is that they are not lost: export the private key for that account, import it into a wallet that supports the network, and move the funds on from there. Phantom adds two cautions worth keeping — importing a private key into another wallet increases its exposure, so move the funds to a fresh account afterwards, and Phantom Support will never ask for your recovery phrase or private key (Phantom Help).

Case three: an exchange deposit

First rule out the harmless explanation. A deposit is credited only after the network confirms it, and Binance notes that how long that takes depends on the blockchain and how busy it is (Binance). A deposit that is still confirming is not lost.

A deposit on a network the exchange does not support for that coin, or without a required memo, is a different matter: it reaches the exchange but not your account. Only the exchange can retrieve it. Binance runs a self-service recovery for some of these cases, including a missing or wrong memo and tokens sent on unsupported EVM networks; it does not cover deposits made to another user’s account or transactions that failed on the blockchain, a fee is charged only if retrieval succeeds, and Binance states that recovery is not guaranteed (Binance). For a missing memo, an approved retrieval returns the deposit to the sending address — and if the memo you typed happens to belong to another user, the deposit may already have gone to them (Binance).

Case four: someone else’s address

Here there is nothing to undo. MetaMask puts it without softening: transactions cannot be reversed nor missing funds restored, and as a self-custodial wallet it cannot intervene (MetaMask Help Center). The only opening is when the address belongs to a platform, whose support may trace the transfer from its ID.

Anyone who asks for your recovery phrase is not helping

Whoever offers to help with a missing transfer, MetaMask’s rule applies: if anyone asks for your Secret Recovery Phrase or private keys, they are trying to steal all of your assets (MetaMask Help Center). Every legitimate route above runs through your own wallet or the exchange’s own support pages.

Next time

Each of these cases can be prevented at the same step: choosing the network by looking at the receiving side. Choose it there first, as Binance’s own deposit guidance asks (Binance) — the steps are in sending USDT to Binance and sending USDT from Binance.