Shepley Capital

WALLETS & SECURITY

Wallets and Security - Cryptopedia by Shepley Capital

What to Do if You Send Crypto to the Wrong Address

Sending cryptocurrency to the wrong address is one of the most distressing experiences in crypto. Unlike a bank transfer, there is no customer service line you can call to reverse the transaction. Blockchain transactions are immutable: once confirmed, they cannot be reversed or recalled by the sender. However, the outcome depends entirely on the specific circumstances, and in some situations, recovery is possible. Understanding what to do immediately, which scenarios offer a chance of recovery, and how to prevent this from happening again is essential for every crypto user.

 

Can You Reverse a Crypto Transaction?

In the vast majority of cases, no. The fundamental property of public blockchains is that confirmed transactions are permanent and irreversible. There is no central authority with the ability to reverse or freeze a transaction once it has been included in a confirmed block. Bitcoin transactions confirmed with six or more block confirmations are considered final. Ethereum transactions are similarly final after confirmation, typically within seconds to minutes. Solana transactions finalise in under a second. Once the transaction is confirmed and the recipient address has received the funds, those funds are under the control of whoever holds the private key for that address, not you.

 

Scenario 1: Sent to an Exchange Address

The most hopeful scenario is sending crypto to an address belonging to a centralised exchange, such as CoinSpot, Swyftx, or Binance. Exchanges control large numbers of deposit addresses and may be able to identify an errant transaction and credit it to you, or return it, if you can provide sufficient evidence. Contact the exchange’s support immediately with your transaction hash (obtainable from a blockchain explorer), the sending wallet address, the receiving address, the asset, the amount, and the timestamp. Act quickly, as exchanges process large volumes of transactions and funds may move to cold storage before support can intervene. There is no guarantee of recovery, and exchanges may charge a fee for transaction recovery services, but this is the best-case scenario.

 

Scenario 2: Sent to Your Own Wallet on the Wrong Network

A common mistake is sending assets to the correct address format but on the wrong network, for example sending ETH to your own Ethereum address via the BNB Smart Chain instead of Ethereum mainnet. In this case, because EVM-compatible chains share the same address format, the receiving address is technically yours: you just need to access the funds on the chain where they arrived. Add the correct network to your MetaMask or other EVM wallet and check your balance on that chain. The funds are likely still in your wallet, simply on a different network than intended. A cross-chain bridge may be needed to move them back to the intended chain.

 

Scenario 3: Sent to a Dead or Burn Address

If you accidentally sent crypto to a known burn address (such as 0x000000000000000000000000000000000000dEaD on Ethereum) or any address where the private key is known to be uncontrolled, the funds are effectively lost. Similarly, if you sent to a correctly formatted address that belongs to no known wallet (a random character string that happens to form a valid address), the funds are mathematically recoverable only by whoever holds the private key for that address, which in practice means no one. This is the worst-case scenario and represents a permanent loss.

 

Scenario 4: Typed the Wrong Address

If you typed an address manually (rather than copying and pasting) and made a typographical error, the funds may have gone to a valid but incorrect address. Most blockchain address formats include a checksum that catches many common typing errors, but not all. If the address you sent to is valid, those funds are now in someone else’s wallet (or an uncontrolled wallet). There is no mechanism to recover from this situation on most blockchains. This underscores the critical importance of always copying and pasting addresses rather than typing them, and always verifying the first and last few characters of the pasted address before confirming the transaction.

 

Immediate Steps to Take

The moment you realise you have sent to the wrong address, take these steps in order. First, check a blockchain explorer using your transaction hash to confirm the transaction is on-chain and see the receiving address. Second, determine which scenario applies (exchange address, own wallet on wrong network, or unknown address). Third, if the receiving address belongs to an exchange, contact their support immediately with full transaction details. Fourth, if you believe the address belongs to someone you know, contact them directly. Fifth, document everything: save screenshots of the transaction details for any potential insurance, tax, or legal purposes. The ATO’s guidance on crypto losses may allow you to claim a capital loss if funds are genuinely unrecoverable.

 

Wallet Address Poisoning Attacks

A particularly insidious attack that causes incorrect address submissions is wallet address poisoning. In this scam, an attacker sends a tiny amount of crypto (often a dust transaction) from an address that visually resembles your own address or a frequently used recipient address. When you later copy a recent address from your transaction history without careful verification, you may copy the attacker’s address rather than the intended one. Because the attacker’s address is similar at the start and end (the parts most users check), it can fool a quick glance. The only complete defence is verifying the entire address character by character before confirming any transaction.

 

Prevention: The Non-Negotiable Rules

Preventing wrong-address sends requires consistent habits applied without exception. Always copy and paste addresses: never type them manually. Always verify the first six and last six characters of the pasted address before confirming. Send a small test transaction of a few dollars before sending a large amount to a new address. Use your wallet’s address book feature to save frequently used addresses under a label rather than copying from transaction history each time. Be alert to clipboard hijacking malware, which replaces copied addresses with the attacker’s address in your clipboard: always re-verify the pasted address after pasting. For very large transactions, consider verifying the address via a second channel of communication with the recipient. Our guide on safely sending and receiving cryptocurrency covers all these practices in detail.

 

Network Mismatch Prevention

Sending assets on the wrong network (for example, sending USDC as an ERC-20 token on Ethereum when the recipient expected USDC on Solana) is another common and costly mistake. Before sending, always confirm: which asset you are sending, which network you are sending it on, and which network the recipient expects. Exchange deposit addresses are often network-specific: depositing ETH to a Binance ERC-20 deposit address when you send it on Polygon is a different asset entirely and may not credit. Read deposit instructions carefully and never assume the same address works across networks unless explicitly confirmed.

 

Key Takeaways

Crypto transactions are irreversible once confirmed on the blockchain. Recovery is possible only in limited scenarios: sending to an exchange address (contact support immediately), or sending to your own wallet on the wrong network (switch networks in your wallet). For all other wrong-address sends, the funds are likely permanently lost. Always copy and paste addresses, verify them character by character, and send a test transaction before sending large amounts. Prevent address poisoning attacks by verifying the full address rather than just the first and last characters. These habits, practised consistently, make wrong-address sends an avoidable mistake rather than an eventual inevitability.

WRITTEN & REVIEWED BY Chris Shepley

UPDATED: MARCH 2026

Choose your next topic from our Cryptopedia​