Recovering coins after pasting an address from a different network into a swap form

05 September 2026

You cannot recover coins that have been sent to an address on the wrong network unless you control the private key for that address on that network. If you sent funds to an address that belongs to you on a different chain, recovery is possible but requires careful steps. If you sent funds to an exchange or swap provider’s address on the wrong network, recovery is usually impossible.

Why this happens

Swap forms ask for a destination address. If you copy an address from a wallet that is set to a different network - for example, pasting a BNB Smart Chain address into a form expecting an Ethereum address - the form will still accept it. The underlying blockchain has no way to know the address was meant for another network. A valid address is just a string of characters; the network only checks that it is formatted correctly. The transaction will confirm on the source chain, and the coins will arrive at that address on the destination chain. But the recipient’s wallet on the destination chain may not control the private key for that address.

The most common scenario: you control both addresses

If you accidentally sent coins to your own wallet address on a different network, you still own the private key for that address on the source network. But the private key is the same across all networks that use the same elliptic curve (Ethereum, BNB Smart Chain, Polygon, Avalanche C-chain, and many others). This means you can access the coins on the wrong network by importing the same private key into a wallet that supports that network.

For example, if you sent Ethereum to your BNB Smart Chain address, you can import your Ethereum private key into a BNB Smart Chain wallet (like MetaMask configured for BSC). The coins will appear there. You can then send them back to the correct network via a bridge or swap.

The worst case: you sent to an exchange or swap provider

If you pasted an exchange deposit address from a different network, the exchange’s wallet on that network may not be controlled by the same private key. Most exchanges generate separate addresses per network. They do not monitor wrong-network deposits. The coins are effectively lost to the exchange’s control. Some large exchanges occasionally recover such funds manually, but they are under no obligation to do so. Smaller swap providers almost never have the infrastructure or incentive to recover them.

Steps to take immediately

1. Do not send more coins. Any further attempts to “fix” the mistake by sending another transaction will only compound the loss.
2. Check if you control the destination address on the wrong network. If you own the private key (e.g., you generated the address from a hardware wallet or seed phrase), you can recover the coins by importing the key into a wallet for that network.
3. If you sent to an exchange, contact support. Provide the transaction hash, the destination address, and the network you used. Be prepared for a long wait and a likely refusal. Do not expect a refund.
4. If you sent to a swap provider, check their documentation. Some providers have a manual recovery process, but most do not. The exchange mentioned in the swap form is not named here; the site routes swaps through several, and none guarantees recovery.

Preventing this mistake

The hub page “Swapping crypto safely” covers the checks you should make before any transaction. The most important single check: confirm that the destination network matches the network you are sending from. Every swap form on this site shows the network of the destination address. Read it. Then read it again. If it says “BNB Smart Chain” and you are sending Ethereum, stop.

When recovery is impossible

If you do not control the private key for the address on the wrong network, and the recipient does not respond or cannot help, the coins are gone. No transaction can be reversed on a blockchain. No third party can force a refund. The only honest answer is that you have lost those coins. Learn from the mistake. Next time, verify the network before you paste.

Back to getting started