After approving a cross-chain swap, wait for the source transaction to confirm, then check that the destination transaction completes before treating the funds as available. Approval usually grants a contract permission to use a token; it does not, by itself, move the token to another chain. If you need the broader route and transfer steps, read how Rango Bridge moves tokens between chains. This guide focuses on what happens after you start from your wallet.
Rango Exchange, at rangobridge.com, is a service that finds and executes cross-chain routes. Rango Bridge can select a route that combines a swap with a bridge, so the token arriving on the destination chain may differ from the one you sent. The exact sequence depends on the route’s protocols.
An ERC-20 token on Ethereum often needs an approval transaction before a swap contract can spend it. Your wallet will show that transaction separately from the swap itself. Once it confirms, you still need to submit and confirm the swap transaction; approving alone leaves the token where it is.
For example, imagine moving a token from Ethereum to Solana. The route may first swap your source token into an asset a bridge protocol accepts, then transfer value across, then swap into a Solana token. A route aggregator coordinates those actions across protocols; it does not make every route a single on-chain transaction.
Each on-chain action has its own transaction record. The source transaction hash proves what you submitted on Ethereum, while destination activity is recorded on Solana. Save the source hash and keep the wallet open until the route reports a destination result. Confirmation on the first chain does not mean the destination transfer has finished.
After the source transaction confirms, the bridge mechanism must recognize it as final enough to act. Some routes lock or escrow assets on the source side and release or mint value on the destination; others use liquidity already available there. A relayer or protocol may pass a verified message between chains. For example, LayerZero provides messaging infrastructure that applications can use, but the application’s route determines what happens to the assets.
Timing depends on the source chain’s confirmation rules, the bridge protocol, and destination execution. The deciding signal is a completed destination transaction or a clear failed status, not simply a spinning wallet or a confirmed source hash. If the source is confirmed but the destination is still pending, check the same route’s status before submitting anything again. A second send can create a second transfer.
Before signing the swap, compare the estimated destination amount with the minimum amount you will accept. Slippage is the difference between the quoted and executed swap rate; the minimum protects against receiving less than that threshold. Network gas pays for on-chain transactions, while route and protocol fees may also affect the amount received. These vary with the route, network conditions, and trade size, so use the live quote rather than assuming one fixed fee.
Wallet prompts are the key safety check: confirm the token, network, and contract permission match the action you intended. If an approval offers a spending limit, an exact allowance reduces how much the contract can use. Never share your recovery phrase to complete a transfer.
In short: approval permits spending, the source transaction starts the route, and destination confirmation tells you when the funds have arrived.