What happens if you send a coin to the right address but on the wrong network during a swap

05 September 2026

The coins are lost, permanently and irrecoverably. The right address on the wrong network is, from the perspective of that blockchain, simply the wrong address.

To understand why, you need to separate the idea of an "address" from the network it lives on. Every blockchain has its own address format. Bitcoin addresses start with 1, 3, or bc1. Ethereum addresses are 0x-prefixed hex strings. Solana addresses are base58. When you send a token, the transaction is broadcast to one specific network. That network validates the address syntax according to its own rules. If the address you paste happens to be valid on the receiving network - say, an Ethereum address when you are sending on Ethereum - the transaction will be accepted. The coins arrive at that address. But the intended recipient, who gave you an address on a different network, does not control that address on this network. Nobody does, or someone else does. Either way, you cannot reverse the transaction.

Consider a concrete case. You are swapping USDC from Ethereum to Polygon. The exchanger gives you a Polygon address that looks like 0xabc…123. You copy it. But you send your USDC on the Ethereum network, to that same 0xabc…123 address. The Ethereum blockchain sees a valid 0x-address, processes the transaction, and credits the USDC to 0xabc…123 on Ethereum. That address on Ethereum is almost certainly a contract or a wallet that the exchanger does not control. The exchanger is watching the Polygon network for your funds. They never see them. Your USDC sits on Ethereum, owned by whoever holds the private key for that address - which is not you, and not the exchanger.

Some exchanges and swapping services run automated recovery tools for very common mistakes. If you send to a major exchange's deposit address on the wrong network, and that exchange also operates on the network you used, they may be able to sweep the funds internally. This is not guaranteed. It is a courtesy, not a right. For a non-custodial cross-chain swap - the subject of the hub page "Swapping crypto across chains" - there is no central operator who can intervene. The swap is executed by smart contracts or peer-to-peer protocols. No human sees the transaction. No button exists to reverse it.

The same logic applies if you send a token that exists on multiple networks to the correct address but on the wrong network. USDT on Ethereum is a different staking/staking-smart-contract-exploit-risks/">smart contract than USDT on Tron. Sending Ethereum USDT to a Tron address fails, because the Tron network rejects the Ethereum-formatted transaction outright. That is a better outcome: the transaction never confirms. But sending Ethereum USDT to an Ethereum address that the recipient controls on Tron - which is impossible, because the same private key produces different addresses on different networks - is the scenario that loses coins.

The only reliable prevention is to check the network field before you click send. Every wallet and exchange displays it. Read it. Match it to what the swap interface told you. If the swap interface says "send on Polygon," do not send on Ethereum. If you are unsure, stop. The hub page on cross-chain swapping explains the mechanics of how assets move without a bridge, and why network discipline is the single most common failure point.

Recovery attempts exist, but they are technical, expensive, and often fail. You can try to convince the owner of the mistaken-address private key to return the funds. That owner is usually a random user or a contract with no recovery function. You can hire a developer to attempt a private key recovery if the address was generated deterministically from a known seed - this almost never applies. In practice, the coins are gone. The network does not care about your intent. It only executes what you signed.

Back to staking