> For the complete documentation index, see [llms.txt](https://lifi-bridge.gitbook.io/lifi-bridge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lifi-bridge.gitbook.io/lifi-bridge/what-is-lifi-bridge-how-cross-chain-routing-works.md).
# What Is LiFi Bridge? How Cross-Chain Routing Works
LiFi Bridge helps solve a common multichain problem: you have funds on one network, but the app, token, or opportunity you want is on another. Instead of manually comparing bridges, swaps, gas costs, and route details across Ethereum, Arbitrum, Optimism, Base, Polygon, and other L2s, [LiFi Bridge](https://lifibridge.app/) helps find a workable route.
That matters because a cross-chain transfer is rarely one clean action. You may need to bridge a token, swap it, receive a different asset on the destination chain, or choose between routes with different fees and wait times. A good route can save money, reduce steps, and help you avoid sending funds to the wrong place.
The simple version: LiFi Bridge is not a single bridge and not a single AMM. It is a cross-chain bridge and route aggregator. It checks bridge and DEX options, then helps route your transfer using the best available path for the action you are trying to take.
### What LiFi Bridge Actually Does
LiFi Bridge sits in the middle of a messy multichain process and makes routes easier to compare. When you choose a source chain, destination chain, token, and amount, it can look across bridge and DEX liquidity sources to build a route.
That route may be simple. For example, you might bridge a stablecoin from Ethereum to Base and receive the same stablecoin on Base.
It may also involve bridging plus swapping. For example, you might start with one token on Arbitrum and receive a different token on Polygon. That is where routing becomes useful, because the best path is not always obvious.
The quote can reflect several moving parts:
* The token you are sending
* The token you expect to receive
* The source chain and destination chain
* Bridge fee or protocol cost
* Gas fees on the source chain
* Possible gas needs on the destination chain
* Slippage and price impact if a swap is part of the route
* Estimated completion time
Fees, liquidity, and network conditions change. A route that looks good now may not be the best route later.
### What You'll Need
Before using a cross-chain bridge aggregator, get the basics ready:
* A non-custodial wallet, such as MetaMask
* Funds on the source chain
* A clear destination chain, such as Arbitrum, Optimism, Base, or Polygon
* The token you want to send or the token you want to receive
* A little crypto for gas on the source chain
* Enough patience to review the quote before approving anything
Most mistakes happen when people rush. Cross-chain transfers involve real money, multiple networks, and wallet approvals. Slow down before you click confirm.
### How Cross-Chain Routing Works in Practice
Step 1: Connect your wallet.
Open the app and connect the wallet that holds the funds you want to move. If you use MetaMask, make sure you are on the correct account.
Step 2: Pick your source chain.
The source chain is where your funds are now. This might be Ethereum mainnet, Arbitrum, Optimism, Base, Polygon, or another supported network. Check the network and token balance before moving forward.
Step 3: Pick your destination chain.
The destination chain is where you want the funds to arrive. Sending assets to Base is not the same as sending them to Arbitrum, even if the token symbol looks similar. Match the destination chain to the app or wallet activity you plan to use next.
Step 4: Choose the token and amount.
Select what you want to send and how much. If you are bridging plus swapping, check what token you will receive on the other side. Do not rely on the token ticker alone. Look at the chain, asset, and expected output.
Step 5: Review the route.
This is the high-value part of using [LiFi Bridge](https://lifibridge.app/): review the suggested route before you approve it. Look at the estimated output, bridge fee, gas fee, wait time, and whether the route includes a swap. If there is a swap, check slippage and price impact. Faster routes may cost more. Cheaper routes may take longer.
Step 6: Approve the token if needed.
Some tokens require an approval transaction before the bridge or swap can use them. This is normal for many DeFi actions, but it still costs gas. Confirm the token and site before signing.
Step 7: Confirm the transfer.
After approval, submit the transaction. Your wallet will show a gas estimate. Network fees move quickly, especially on busy chains. If the cost looks too high, quote again later.
Step 8: Track the arrival.
Cross-chain transfers are not always instant. Some routes complete quickly; others need more time. Keep the page open if possible, and do not start duplicate transfers just because the first one is pending. Check the destination chain in your wallet once the route says it is complete.
### Common Mistakes That Cost People Money
Wrong destination chain. The most common mistake is sending funds to a chain that does not match the app you wanted to use. Before confirming, say it plainly: "I am sending from this chain to that chain."
Wrong token expectation. Bridging one token and receiving another can be useful, but only if you meant to do it. If a route includes a swap, review the output token, slippage, and price impact.
Ignoring gas. You need gas on the source chain to send the transaction. You may also need gas on the destination chain for later actions. Do not bridge your entire balance if it leaves you unable to use the funds afterward.
Only checking speed. The fastest route is not automatically the best route. Compare expected output, fees, and wait time together.
Using unofficial front-ends. Search results, ads, and copied links can be risky. Use the correct site and check the URL before connecting a wallet or signing approvals.
Assuming there is no risk. Bridges and smart contracts carry risk. Wallet mistakes, bad approvals, chain confusion, gas fees, and smart-contract issues can all matter. A route aggregator can make the process easier, but not risk-free.
### Use LiFi Bridge With a Clear Plan
A good cross-chain transfer starts before you click confirm. Know your source chain, destination chain, token, amount, expected output, fees, and approximate wait time. Check the route, understand whether it includes a swap, and keep enough gas for the actions that come next.
If you want a simpler way to compare routes instead of manually testing bridges and DEXs one by one, use [LiFi Bridge](https://lifibridge.app/) as the next step for planning and executing a cross-chain transfer.
---
# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://lifi-bridge.gitbook.io/lifi-bridge/what-is-lifi-bridge-how-cross-chain-routing-works.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.