Sent Crypto to the Wrong Address: What Still Works and What Is Gone for Good

The information provided in this article is for informational purposes only and does not constitute financial advice. Investing in cryptocurrencies involves a high level of risk.

"Once sent, gone forever" is the line everyone knows, and it is only half right. A confirmed transaction genuinely cannot be reversed. But whether your money stays reachable is not decided by the blockchain. It is decided by whoever holds the private key to the destination address.

In four of six typical cases, that key sits with someone you can reach: you yourself, or your exchange. Only in two cases is the outcome final. Before you do anything else, work out which case you are in.

Key takeaways

• The transaction itself is not the problem. What matters is who controls the key to the destination address.
• On EVM chains such as Ethereum, Arbitrum or Polygon, the same address belongs to the same key, so sending over the wrong network is usually not a loss.
• For deposits that reach an exchange over the wrong network, some providers run a recovery procedure. Binance quotes up to 30 business days and 20 USDT for unsupported EVM networks, with no guarantee of success.
• Chainalysis identified at least 82,031 suspected spoofed addresses from a single address poisoning campaign on Ethereum between February 28 and May 4, 2024, causing $69.7 million in damage (report dated October 23, 2024).
• The Bech32 checksum is guaranteed to catch every error involving at most four substituted characters, which is why plain typos rarely slip through.
• Any service that promises to retrieve sent coins against an upfront payment is a scam. There is no technical basis for it.

Wrong address, first step: sort your case

Open the block explorer for the chain in question and look up your transaction by its transaction ID. You need two pieces of information: is it confirmed, and which recipient address does it name? Then place your case in the table below:

Everything that follows hangs on that classification. Skip it, and you lose time on support tickets at places that can do nothing technically, or you write off a position that was still within reach.

Wrong address on the right network: the hard case

If you sent funds to a stranger's wallet address, the situation is unpleasantly clear. There is no freeze, no chargeback and no authority that could step in. Technically, the coins now belong to whoever holds the key.

That leaves exactly one route: contact the person, provided the address can be attributed to someone, for instance because it belongs to a known service. For meaningful amounts, filing a criminal complaint also makes sense, because investigators can obtain identities through exchanges that you cannot reach yourself. Manage your expectations, though. With small amounts this practically never leads anywhere.

The same applies to tokens that end up at a contract address by accident. Some contracts have a recovery function, most do not.

Wrong address through the wrong network: the recoverable case

Here comes the good news, and it is less widely known than it should be.

Ethereum and the chains compatible with it, namely Arbitrum, Optimism, Polygon, BNB Chain and Base, derive addresses from the same key format. With a normal wallet address, your address on Arbitrum is the same string as on Ethereum, and the same private key opens both. Anyone who sent tokens to their own address over the wrong one of these chains has lost nothing. The funds are simply sitting in an unexpected place.

The procedure: add the relevant network in your wallet, make the token visible manually via its contract address if necessary, and it appears. To move it on from there you need a little gas in that network's own currency.

The exception that gets expensive: smart contract wallets

With a smart contract wallet, such as Safe, Argent or an ERC-4337 account, none of this holds. The address there is not derived from a key, it is a contract address. It is the same on another chain and under your control only if the contract was deployed there with identical parameters.

The Optimism case from June 2022 shows how expensive that can get: 20 million OP went to a Safe address that existed on Ethereum but had not been deployed on Optimism. A third party deployed the contract at exactly that address himself and thereby gained access. He returned roughly 17 million tokens voluntarily and kept the rest.

When in doubt, check the block explorer of the destination chain first to see whether any code exists at your address there.

Unrelated chains are a different matter. Bitcoin, Solana and Ethereum use different address formats. A Bitcoin address is not a valid destination on Solana, and as a rule the transaction never goes through in the first place.

Wrong address at an exchange: what support can actually do

If the deposit reached an exchange but over the wrong network, the coins sit at an address whose key the exchange holds. That makes it an organisational problem rather than a technical one.

Many large providers run a dedicated procedure for this. Binance, for example, offers self-service recovery, where users trigger the retrieval themselves from their transaction history. The terms differ sharply by case: for tokens on unsupported EVM networks, Binance quotes up to 30 business days and a fee of 20 USDT; for missing or incorrect memos, 7 business days against the network fee (FAQ as of August 2026). The fee is only retained on successful recovery, but it has to arrive in advance, because processing starts only after that. The provider explicitly guarantees no result. Other exchanges review cases manually, and others again refuse outright for unsupported tokens.

What you need for this: the transaction ID, the destination address, the network used, the token and the timestamp. Supplying those five details in the first ticket typically saves two rounds of follow-up questions.

The second most common case of this kind is the missing identifier. With XRP, Stellar or Cosmos, the exchange assigns deposits using a memo or destination tag. If it is missing, the money sits correctly in the exchange's omnibus account, just without an assignment to you. That is a support case too, and usually a solvable one.

Avoiding the wrong address: the scams built around it

Not every wrong address is your own mistake. In address poisoning, an attacker sends you tiny or worthless amounts from an address whose first and last characters exactly match those of an address you use regularly. The next time you send something, you copy from your transaction history and hit theirs.

Chainalysis measured this scheme on Ethereum in a report dated October 23, 2024: in a single campaign between February 28 and May 4, 2024, at least 82,031 suspected spoofed addresses, 2,774 affected victim addresses and $69.7 million in damage. The largest single case involved around $68 million in Wrapped Bitcoin; the perpetrator returned the amount in Ether on May 9, netting roughly $1.49 million. The hit rate is worth noting: only 0.03 percent of the spoofed addresses received more than $100 from victims at all. The scheme rarely works, but when it does, it works big.

Four habits that shut this down:

1. Use an address book instead of your history, and verify on the device. Set up frequent destinations properly once, then only ever pick them from there. Which wallets ship a usable address book is covered in our comparison of software wallets. A hardware wallet goes one step further: it shows the destination address on its own display, and no malware on your computer reaches that display.
2. Check the whole address, not the start and the end. That shortcut is precisely the attack surface. Reading along four to six characters from the middle costs two seconds.
3. Send a test transaction for larger amounts. A small amount first, wait for it to arrive, then the rest. The network fee for that is cheaper than any misdirected transfer.
4. The checksum helps, but not everywhere. The encoding of modern Bitcoin addresses, Bech32 for bc1q… and Bech32m for Taproot addresses bc1p…, is guaranteed to catch every error affecting at most four substituted characters; beyond that, the probability of missing one is below one in a billion. A slipped character therefore almost always produces an error message rather than a loss. Two gaps remain: in 2024 the Bech32 developers themselves disclosed that their scheme is not always robust against the insertion or deletion of fewer than five consecutive characters, a gap Bech32m closes. And no checksum helps against a valid but wrong address. That is exactly what address poisoning relies on.

A related scheme does not target the address at all, it targets you: fake requests from your exchange to move your balance "to safety". We took apart how to spot those using the example of the phishing messages that followed the MiCA deadline.

Wrong address: what still works while the transaction is unconfirmed

There is a narrow window. As long as a transaction sits in the mempool unconfirmed, the funds still belong to you, and it can be replaced by a competing transaction carrying a higher fee.

On Bitcoin this has been possible without preconditions since Bitcoin Core 29.0 of April 14, 2025: full replace-by-fee is the default behaviour there, and the original transaction no longer needs to signal for it. EVM chains never had that condition. A transaction with the same nonce and a markedly higher fee is enough, usually at least a 10 percent premium.

The only real condition is that no block has confirmed it yet. With an empty mempool that can be a matter of seconds; when the network is busy, you have longer. Do not rely on it regardless, and do not hire anyone who offers to handle it against an upfront payment.

Which brings us to the final point: every provider that promises to retrieve sent coins is a scam. No technology for it exists. Such offers find their victims deliberately in forums and comment threads under reports of losses, and the second loss is then larger than the first.

Frequently asked questions

Can I reverse a confirmed transaction? No. The only thing you can influence is whether someone with access to the destination address sends it back, voluntarily or on request.

I sent to my own address on the wrong network. Is it gone? With a normal wallet address on EVM-compatible chains, as a rule no: the same address there belongs to the same key. Add the network in your wallet, make the token visible, send it on. You will need a little gas in that network's currency. If you use a smart contract wallet, this only applies when the contract exists on the destination chain.

How long does recovery at an exchange take? Depending on the provider and the case, from a few days to several weeks. Binance quotes up to 30 business days and 20 USDT for tokens on unsupported EVM networks, and 7 business days for memo cases; other providers make no firm commitment.

Why does my wallet accept an obviously wrong address? Because it is formally correct. Checksums detect typos, not bad intent. An attacker's valid address looks exactly as right to the software as your own.

Is a criminal complaint worth it for small amounts? Rarely, but it costs nothing except time. It becomes more relevant when the destination address can be attributed to an exchange, because investigators can request identities there that private individuals cannot obtain.

Sources

• Chainalysis: Address Poisoning Scams (October 23, 2024, figures for the campaign of February 28 to May 4, 2024)
• Bitcoin Improvement Proposal: BIP-0173 – Base32 address format for native v0-16 witness outputs (error detection of the Bech32 checksum)
• Binance Support, FAQ "How to Retrieve a Deposit That Hasn't Arrived With Self-Service Recovery?" (binance.com/en/support/faq/how-to-retrieve-a-deposit-that-hasn-t-arrived-with-self-service-recovery-4d1347b4d6d44564ba44ea785703a4fd), accessed on August 12, 2026
• Bitcoin Core: Release Notes 29.0 (April 14, 2025, full replace-by-fee as default)
• Ledger Support: Address Poisoning Scam