How to Send Crypto Across Chains Without Losing It
Moving crypto between chains means either routing it through an exchange that accepts deposits on one network and withdrawals on another, or using a bridge that locks the asset on the source chain and issues a wrapped version on the destination, and in both cases the mistake that costs people money is picking the wrong network on the send screen.
Updated · By RampAtlas Research
Key takeaways
- Crypto moves between chains either through an exchange that accepts a deposit on one network and pays out on another, or through a bridge.
- A token does not travel between chains, so a bridge locks the asset on the source chain and mints a wrapped claim on the destination.
- A wrapped token is only worth the underlying asset while the contract holding that asset remains solvent and unexploited.
- The developer documentation on ethereum.org notes that bridges account for the top three biggest hacks in decentralized finance.
- Choosing the wrong network on a withdrawal screen is the single most common way people lose funds permanently.
In this guide
Moving crypto between chains means either routing it through an exchange that accepts deposits on one network and withdrawals on another, or using a bridge that locks the asset on the source chain and issues a wrapped version on the destination, and in both cases the mistake that costs people money is picking the wrong network on the send screen.
The confusion is understandable. The same ticker appears on several chains, wallets display them identically, and interfaces ask you to choose a network in a dropdown that looks like a formality.
Why a token cannot simply move
A blockchain only knows about its own state. There is no mechanism by which a balance on one chain becomes a balance on another, because neither chain can read the other's ledger.
Everything that looks like a cross-chain transfer is therefore a pair of separate actions with something in between guaranteeing they correspond. Either a company takes custody on one side and pays out on the other, or a contract locks the asset on one side while another contract issues a claim on the other.
Route one: through an exchange
The simplest path for most people is an exchange account. Deposit the asset on the network you currently hold it on, then withdraw it on the network you want, choosing the destination network on the withdrawal screen.
This works because the platform holds real balances on both chains. It is usually the cheapest option for assets and networks a major venue supports, and it avoids smart contract risk entirely. The costs are the deposit and withdrawal fees, the time, and the fact that the funds sit in custodial hands during the transit. Support varies by platform and by asset, so check the specific asset and network on the operator's own documentation. Exchange pages on this site link to those, including Coinbase, Kraken, and Binance, with the full set at Exchanges.
Route two: a bridge
A bridge is infrastructure that connects two chains. The developer documentation on ethereum.org describes bridges as establishing a transportation route between blockchains along which tokens, messages, arbitrary data, and even smart contract calls can be transferred, and identifies locking assets on the source chain while minting assets on the destination chain as one of the primary mechanisms (source: ethereum.org, Blockchain bridges).
That lock-and-mint pattern is where wrapped token assets come from. The original stays locked in a contract on the source chain and a new token is issued on the destination, redeemable one-for-one for the original. It is a claim, and it is worth the underlying asset for exactly as long as the arrangement holding that asset remains solvent and unexploited. The same documentation warns that many bridges use wrapped assets to mint canonical versions of the original asset on a new chain, which exposes the ecosystem to systemic risk, as wrapped versions of tokens have been exploited (source: ethereum.org, Blockchain bridges).
Bridges also differ in what you are trusting. Trusted bridges rely on an external set of verifiers such as a federation with multi-signature control, a multi-party computation system, or an oracle network. Trustless bridges instead rely on the chains they connect and their own validators, without introducing an additional trust assumption (source: ethereum.org, Blockchain bridges). The same page notes that bridges account for the top three biggest hacks in decentralized finance and that the technology remains in early stages of development.
None of that means never use a bridge. It means the amount and the duration matter. Bridging a working balance for an afternoon is a different exposure from parking a long-term holding in a wrapped asset for years.
| Through an exchange | Through a bridge | |
|---|---|---|
| How it works | The platform holds real balances on both chains, takes the deposit on one and pays out on the other | A contract locks the asset on the source chain and mints a claim on the destination |
| Contract risk | None | Yes. Wrapped versions of tokens have been exploited |
| Custody during transit | The funds sit in custodial hands | The funds sit in a locking contract |
| What it costs | Deposit and withdrawal fees, plus time | A fee on the source chain, a fee on the destination chain, and often a fee to the bridge itself |
| Use it when | Both networks are supported for the asset, the amount is large, and you are not in a hurry | No exchange connects the two chains, you are already operating on-chain, and speed matters more than the trust assumption |
The wrong-network mistake
This is the failure that generates the most support tickets and the fewest recoveries.
Every address belongs to a network. Ethereum and chains that copied its address format share the same shape, which is why funds sent to the "same" address on the wrong one of those chains arrive somewhere real rather than bouncing. Where they land depends on what controls that address on the destination chain.
| Where the funds landed | Recovery |
|---|---|
| Your own wallet address on an unsupported chain, and you hold the seed phrase | Usually possible. Add the chain in your wallet, or import the phrase into software that supports it, and the funds appear |
| An exchange deposit address on a network that exchange does not credit | Depends entirely on that exchange's policy. Many decline, or charge a substantial fee |
| A contract address that cannot handle the token | Typically unrecoverable |
Bitcoin and several other chains use address formats that are not interchangeable, so a wrong-network send there usually fails to broadcast rather than misdelivering. That is the friendly version of the error.
Memos and destination tags
Some networks identify a recipient with an address plus a memo or destination tag, and exchanges use one shared address for all customers with the tag telling them whose deposit it is. A deposit sent without the tag does not credit automatically. It is usually recoverable through support, slowly, and it is entirely avoidable by copying both fields.
A procedure that avoids the common losses
- Start from the destination. Open the receiving wallet or exchange deposit screen first, select the exact asset and the exact network there, and copy the address and any memo from that screen.
- Confirm the asset is the same thing on both sides. stablecoin assets are the usual trap: the version of a dollar token issued natively on a chain and a bridged version of the same ticker are different tokens with different contract addresses, and a venue that accepts one may not accept the other. Asset pages such as Tether and USDC list the chains each asset runs on.
- Keep the destination chain's own coin available. Fees on the receiving side are paid in that chain's gas token.
- Send a test transfer. Wait for confirmation and verify arrival on a block explorer for the destination chain rather than trusting the sending interface's status.
- Send the rest, and check the destination address again after pasting. The lookalike-address attacks that target this moment are covered in Address poisoning and clipboard attacks.
Choosing between the routes
Use an exchange when it supports both networks for the asset, when the amount is large, and when you are not in a hurry. It is cheaper, it has a support channel, and it carries no contract risk.
Use a bridge when no exchange connects the two chains you need, when you are already operating on-chain, and when speed matters more than the trust assumption. Prefer bridges with long operating histories and published audits, check that you are on the official domain rather than a clone, and move working amounts rather than savings. The trading and fee context for the assets involved is on the asset pages, starting at Ethereum and Buy Bitcoin.
Frequently Asked Questions
Is a wrapped token the same as the original asset?
No. It is a separate token on a different chain that represents a claim on the original. It tracks the price while the arrangement holding the original works as intended, and it is exposed to the failure of that arrangement in a way the original is not.
What should I do if I sent funds on the wrong network?
Determine which of the three cases applies. If the destination was your own address and you hold the recovery phrase, try importing it into a wallet that supports the destination chain. If it was an exchange deposit address, open a support ticket immediately and expect a policy decision rather than a guarantee. If it was a contract, assume the funds are gone.
Why is bridging sometimes more expensive than the transfer is worth?
You pay a fee on the source chain, a fee on the destination chain, and often a fee to the bridge itself, and busy periods raise the first two. For small amounts the total can exceed the transfer. Check the quoted total before confirming.
Are layer 2 networks bridges?
An Ethereum layer 2 moves value in and out through a bridge contract, but it derives its security from the chain underneath rather than from an external set of verifiers, which is a different trust model from a bridge connecting two independent chains. Withdrawal timing differs by design, and some designs impose a waiting period on the way out.
Can I bridge directly between two wallets I own on different chains?
Bridges operate on addresses, so you can usually specify a destination address you control. Verify the destination chain supports that address format, and send a test amount before committing the rest.