How to move assets across chains without bridging

A bridge is a smart contract that locks tokens on one chain and issues a representation on another. That representation is not the original asset. If the bridge is exploited, the representation can become worthless. The exchange form on this page does not use a bridge. It uses a swap service that matches your deposit to an order and sends a different asset from its own inventory on the destination chain.

The mechanism is straightforward but not obvious. You send your coins to an address the service controls. The service credits your order, then sends the equivalent value from its own wallet on the other chain. The service never locks your tokens in a contract. It takes possession of what you send and gives you something else. This is a trade, not a lock-and-mint.

What happens to your coins during the time between chains in a cross-chain swap. Your coins leave your wallet and arrive at the service's address on the source chain. The service confirms the deposit. Then it sends the destination asset from its own wallet on the target chain. There is a gap. During that gap, your coins are in the service's custody on the source chain. The service has not yet sent the destination asset. If the service were to go offline during that gap, your coins would be stuck at its address. Reputable services have automated systems that recover from interruptions, but the gap is real. You are trusting the service to complete the second leg.

How do you know a swap service is not just a bridge with a different name. A bridge requires you to accept a wrapped or synthetic token. A swap service gives you a native token. If you send ETH on Ethereum and receive SOL on Solana, the SOL is native Solana SOL, not a representation. Check the explorer after the swap. If the destination asset is a contract address rather than the native coin, the service is effectively acting as a bridge. The service should be able to explain how it sources its destination inventory. If it cannot, treat it as a bridge.

How does a swap service match your deposit to your order without an account. The service generates a unique deposit address for each order. That address is derived from your order ID and the destination address you provided. When you send funds to that address, the service reads the transaction and associates it with your order. No login or registration is needed. The deposit address is yours only for that order. After the swap completes, the address is retired. This is why the service asks for a return address before you send anything.

Why do cross-chain swaps ask for a return address before you send anything. The return address is a safety net. If the swap cannot complete - because of a network issue, a token mismatch, or a chain halt - the service needs somewhere to send your funds back. Without a return address, a failed swap leaves your coins in the service's custody indefinitely. The service cannot guess where to return them. You must provide a valid address on the source chain. If you provide the wrong network, the return will fail.

What happens when you send a token directly to a swap service on the wrong network. The service monitors the correct network. If you send on a different network, the transaction never reaches the service's monitoring system. The coins arrive at an address the service controls on that network, but the service has no record of an order for that network. The coins are lost unless the service has a manual recovery process. Most services do not. Always confirm the network before sending.

Why does a swap sometimes route through three or more tokens instead of a direct pair. The service maintains liquidity in certain pairs. If the pair you want is not one of them, the service routes through intermediate tokens. For example, if you want to swap AVAX for MATIC, the service might swap AVAX to USDC on Avalanche, then USDC to MATIC on Polygon. Each hop adds a fee and a delay. The service shows the route before you confirm. You can reject it and find a direct pair elsewhere. The route is a liquidity decision, not a technical requirement.

What is the difference between a liquidity pool swap and a peer-to-peer cross-chain trade. A liquidity pool swap uses a smart contract that holds reserves of both tokens on the same chain. You trade against the pool. A peer-to-peer cross-chain trade matches you with a counterparty who holds the asset you want on the destination chain. The service acts as the intermediary. The peer-to-peer trade is slower because it requires a match. The liquidity pool swap is instant but limited to the pool's depth. Both can be used for cross-chain movement, but only the peer-to-peer model gives you a native asset on the other side.

How do swap services handle a chain halt or fork while your trade is in progress. A chain halt means no transactions confirm on the halted chain. If your deposit is on the halted chain, the service cannot confirm it. The order stays open. The service may wait for the chain to resume. If the halt is indefinite, the service may return your funds after a timeout. A fork creates two versions of the chain. The service follows the chain that the majority of validators recognize. Your deposit may be on the minority fork. The service will not honor that deposit. You must wait for the fork to resolve. The service's terms should specify the timeout and the fork policy. Read them.

What can go wrong and cannot be undone. Sending to the wrong network cannot be undone. Sending a token the service does not support cannot be undone. Providing a wrong return address means the return will fail. The service cannot reverse a completed swap. Once the destination asset is sent, the trade is final. You are relying on the service's operational reliability. Check the service's transaction history on the destination chain. Look for long gaps between deposit and payout. Avoid services that show frequent incomplete swaps.

The form below will generate a deposit address and ask for your return address. Confirm the network, the token, and the amount. After you send, the page will update with the destination transaction. That transaction is the only proof that the swap is done.