What happens if you send coins to the right address but on the wrong network

05 September 2026

Your coins become unrecoverable on the destination chain, in almost every case. You will not receive any asset on the intended network, and the funds are lost because the private key controlling the address exists on a blockchain that does not recognise the transaction.

The problem is not the address format. It is the network itself. Crypto addresses are derived from a private key, and the same private key can produce addresses on many different blockchains. However, each blockchain operates its own independent ledger. If you broadcast a transaction on Ethereum (ERC-20) using an address that looks valid on BNB Smart Chain (BEP-20), the Ethereum network will process the transaction normally. The recipient sees nothing, because the recipient’s Ethereum wallet never expected tokens from BNB Chain. The sender sees the transaction confirmed on Ethereum. The coins are now controlled by the address on Ethereum, not by the address on BNB Chain.

The recipient’s private key controls that address on Ethereum. If the recipient knows that private key, they can import it into an Ethereum wallet and recover the tokens. Most users do not check, because they generated that private key for BNB Smart Chain and never considered using it on Ethereum. Even if they do, the process requires them to locate the private key, import it into a wallet supporting both chains, and then manually move the funds. This is a burden many users will never accept or understand.

Wrapped tokens complicate matters further. A wrapped bitcoin on Ethereum (WBTC) is not bitcoin. Sending actual bitcoin to an ERC-20 address does not produce WBTC. The bitcoin transaction will be broadcast on the Bitcoin network, and the address will not be recognised as valid because Bitcoin addresses use a different format and checksum. The transaction will fail or be rejected. In that case, the send fails outright. The coins return to the sender, but some wallets or exchanges may charge a fee for the failed attempt.

Exchange deposits behave differently. Centralised exchanges assign a single deposit address for each asset. If you send tokens to that address on the wrong network, the exchange may still credit your account if they support that network and can detect the mismatch manually. This is not guaranteed. Most exchanges will not see the transaction on the intended chain and will not credit you. Recovery is possible if you contact support, but it can take weeks and incur heavy fees. Some exchanges never recover the funds.

Cross-chain swaps avoid this entirely. The hub page "Swapping crypto across chains" explains a method where you never directly send coins to an address on the wrong network. Instead, you deposit into the exchanger, it handles the bridging internally, and you receive the correct asset on the correct chain. No address reuse across networks is required.

The only practical protection is to check the network before you confirm a transaction. Wallets and exchange interfaces now display network names prominently. Even so, a moment of inattention is all it takes. Many users have lost funds by copying an address from one wallet and pasting it into a different network’s field. The address looks identical. The result is not.

If you send coins to the right address on the wrong network, the funds are technically available on the other chain, but only if the recipient controls the private key and knows to look for them. In practice, that rarely happens. Treat any outbound transaction as final. Verify the network three times. The same principle applies when using a cross-chain swap: the exchanger handles the network correctly, but the user still chooses where the funds go. One mistake in that choice can produce the same outcome.

Back to ethereum