> 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/bungee-bridge-which-route-fits-your-wallet-transfer.md).

# Bungee Bridge: Which Route Fits Your Wallet Transfer?

A bungee bridge compares ways to move tokens between blockchains. Some routes also swap your token, so you arrive with the asset you need.

On a centralised exchange, you may choose a network when withdrawing. From your own wallet, you also choose how the transfer crosses chains. That choice affects the token you receive, the cost, and the wait.

### What does a bungee bridge do?

It gathers possible cross-chain routes so you can compare them before sending tokens. A route is the full path from your starting token and network to your target token and network. The aggregator finds paths; the underlying bridge carries out the transfer.

Say you hold USDC, a dollar-linked token, on Arbitrum and need it on Optimism. To compare paths for that transfer, the [bungee bridge](https://bungeebridge.co) finds routes through different cross-chain protocols. A Bungee crypto bridge route can also include a swap if the token you need differs from the one you hold.

Start by naming the result you want: the destination chain, token, and amount. “USDC on Optimism” is more useful than “move my USDC.” The same token name can refer to different versions on a chain, so check the exact token you expect to receive.

### Which route types fit different transfers?

There are four common route shapes, based on where a token swap happens. A swap trades one token for another. The simplest route that delivers the right token is usually the easiest to assess.

* **Direct bridge —** Best when you want the same token on another chain, such as USDC from Arbitrum to Optimism. It does not fit when that token cannot travel on the available bridge or you need another asset at the end.
* **Swap, then bridge —** Best when your starting token cannot be bridged directly, but another token can. It does not fit well if the first trade has a poor price or adds too much cost.
* **Bridge, then swap —** Best when the target token is easier to buy on the destination chain. It may disappoint when trading there is thin, meaning a larger trade moves the price more.
* **Swap on both sides —** Best when neither your starting nor target token has a direct bridge path. It adds two trades, so compare the final amount carefully.

These describe what happens to your tokens, not who provides the bridge. A Bungee token bridge route may use a direct transfer for one pair and a swap route for another. The deciding detail is the token that lands in your wallet, after every step.

### How does a route move value between chains?

A route records your payment on the starting chain and delivers tokens on the destination chain. The tokens do not physically travel between networks. Each chain keeps its own record, and a bridge connects the two actions.

A liquidity bridge can deliver quickly by using tokens already available on the destination chain. With a protocol such as Across Protocol, a relayer—an operator supplying those tokens—can pay the recipient first. The protocol checks the original payment and repays the relayer later. Hop Protocol is another example of a bridge protocol.

A canonical bridge is a chain’s official bridge route. It can have a different wait from a liquidity route. For example, withdrawing through Arbitrum’s official bridge to Ethereum takes at least seven days because of its dispute period. A route that looks cheaper may therefore be unsuitable when you need the funds today.

### What sets the amount received and the wait?

Your final amount reflects bridge charges, any swap price, and network transaction costs called gas. Gas is paid to process an action on a chain, usually in that chain’s native token. The amount received matters more than a single fee shown on its own.

For an illustrative comparison, suppose one route sends 1,000 USDC and quotes 997.50 USDC received. Another quotes 996.80 USDC but expects a shorter wait. The 70-cent difference may matter little for an urgent transfer, while a long wait may matter a lot. These are examples, not current quotes.

Quotes can change before you confirm. A swap may also have slippage: the gap between the quoted price and the execution price. Check the minimum amount you would receive, the estimated time, and any source-chain gas before approving the transfer.

### How do you choose and send a route?

Choose the route by its final token, final amount, and expected arrival time. First, confirm the destination network and receiving address. Then compare complete routes for the amount you plan to send, rather than judging a bridge fee alone.

Your wallet may ask for a token approval before the transfer. Approval gives a contract permission to use that token; the transfer is a separate action. Keep enough native token for source-chain gas, read what each wallet request authorises, and check the destination wallet after the transfer completes. If a transfer is pending, check its status before sending it again.

#### Do I need gas on both chains?

You need enough gas on the starting chain to submit the transaction. You may also need the destination chain’s native token to use the funds after they arrive. That depends on what you plan to do next and what the route delivers. For example, receiving USDC on Optimism does not itself give your wallet ETH for a later transaction.

#### Why might the same token name have several versions?

A chain may have a native version of a token and versions issued through different bridges. They can share a familiar name while having different contract addresses, which identify the exact token. If you plan to deposit the result elsewhere, check which version that destination accepts before choosing a route. The bungee bridge comparison only helps if the quoted output is the token you actually need.

Pick the route that delivers the right token on the right chain at an acceptable total cost and wait.


---

# 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 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/bungee-bridge-which-route-fits-your-wallet-transfer.md?ask=<question>&goal=<user_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 `automate deployments from our CI pipeline` 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.
