> For the complete documentation index, see [llms.txt](https://aboutcryptotalks.gitbook.io/aboutcrypto/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aboutcryptotalks.gitbook.io/aboutcrypto/rango-bridge-routes-for-moving-crypto-across-chains.md). # Rango bridge: Routes for Moving Crypto Across Chains Use Rango bridge to find a route when you need to move or swap crypto between blockchains, especially after a failed attempt. Once you have confirmed the first transfer failed, [Rango bridge](https://rangobridge.com) can help you find another route for your source asset and destination. That route may bridge the asset, swap it, or do both. ### How Does Rango bridge Find a Route? It compares ways to get from the token you hold on one chain to the token you want on another. A route can include a decentralized exchange (DEX) trade, a cross-chain transfer, and a second trade on the destination chain. Your source transaction starts the process, but its confirmation alone does not mean the destination transfer has finished. rangobridge.com is a cross-chain DEX and bridge aggregator that routes swaps across many blockchains. A Rango cross-chain swap may combine a DEX trade with a bridge transfer when the token you hold cannot move directly to the destination in the form you need. Ethereum.org’s bridge documentation describes several ways value can cross chains: tokens may be locked on one chain and represented on another, burned and minted, or exchanged through liquidity. That distinction matters if you need a particular token contract. Two assets called “USDC” on the same destination can have different issuers or bridge origins, and a receiving app may accept only one of them. ### Which Route Type Fits What You Need? The deciding question is what asset must arrive, including its network and token contract. These route types describe the main paths an aggregator may compare; a longer route can combine more than one. * **Same-asset bridge transfer:** Best when you already hold the asset you need and the destination form is acceptable. A liquidity bridge such as Stargate illustrates one way to move value between chains. This route does not fit if the recipient needs a different token or a different representation of the same ticker. * **Swap, then bridge:** Best when your input token has a liquid DEX market on the source chain but is not itself the asset used for the cross-chain leg. A source trade, potentially through a DEX such as Uniswap, converts it first. It fits poorly when that initial trade has thin liquidity and high price impact. * **Bridge, then swap:** Best when the desired token is available through a liquid market on the destination chain. The bridge delivers an intermediate asset, which is traded after arrival. It may not fit if destination liquidity is thin or the route leaves you without the native coin needed for a separate destination transaction. * **Native cross-chain swap:** Best when you want one chain’s native coin in exchange for another’s, rather than a wrapped version. THORChain’s documentation describes native BTC-to-ETH swaps using its liquidity pools as an example. This type does not fit a pair that its underlying protocol cannot handle or a request for a specific bridged token. Suppose, as an example, you hold $1,000 of USDC on Ethereum and need SOL on Solana. A same-asset transfer would leave you with USDC, so it would miss your goal. A route that moves a suitable intermediate asset and ends with a swap to SOL addresses the actual request; compare the quoted SOL received, not only the bridge charge. ### What Sets the Cost and Arrival Time? Cost depends on every leg: source-chain gas, any bridge or protocol charge, DEX trading fees, price impact, and any destination execution cost. Gas is the network payment for processing a transaction; price impact is the change in the swap rate caused by the trade’s size relative to available liquidity. Check the final amount of the requested token and any gas paid separately. For an illustrative $1,000 transfer, a route might deliver $992 of destination value after a $3 bridge charge and $5 of trading costs, while charging $6 in source gas separately. Its total economic cost is then about $14, even though the output is only $8 below the input. Actual amounts vary with the chains, route, trade size, and network demand; a quote is an estimate until its transactions execute. Arrival time has separate stages: source confirmation, the bridge’s required confirmations or settlement, and destination execution. A transfer may therefore remain pending after its source transaction succeeds. Routes using available destination liquidity can settle in minutes, while confirmation rules or a withdrawal period can make other routes take much longer; check the route’s stated timing before sending. ### What Should You Do If a Transfer Is Pending or Failed? First, use the transaction hash to check the source-chain result. A common mistake is to see “confirmed” on the source chain and submit the transfer again. That confirmation may show only that funds entered the bridge; check whether the destination leg has completed before creating a second transfer. If the source transaction reverted, the transfer did not start, although gas may have been spent. If the confirmed transaction was only a token approval, it authorized spending but did not move the token across chains. Identify which transaction actually sent the asset, then check the destination address and the expected token contract on the destination chain; an arrived token can be absent from a wallet’s default asset list. If the source transfer succeeded but the destination asset has not arrived, keep the transaction hash and route details for the underlying protocol’s status or recovery process. Before any new attempt, verify the destination network, address, and exact token you need, then compare routes for that combination. Wait for the first transfer to reach a clear outcome before sending the funds again. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://aboutcryptotalks.gitbook.io/aboutcrypto/rango-bridge-routes-for-moving-crypto-across-chains.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.