What LI.FI is (and is not)
LI.FI aggregates liquidity and bridge endpoints behind a unified API. When you ask for a quote, LI.FI evaluates competing paths — maybe a canonical bridge, maybe a DEX swap into a bridgeable asset, maybe several hops — and returns executable calldata for wallets.
LI.FI is not a custodian. It does not hold your seed phrase. It is also not a guarantee of best human-visible price: quotes are snapshots subject to competition, gas, and bridge capacity. Your wallet still must simulate, display, and obtain your signature.
What a LI.FI quote contains
Wallet-relevant fields (names may vary slightly by API version) include:
- Expected output — what the route aims to deliver at quote time.
toAmountMin— minimum acceptable output given slippage settings; if on-chain conditions would deliver less, the transaction should revert rather than underpay you silently.- Gas estimates — expected cost on source (and sometimes hints for destination steps).
executionDuration— rough time until funds arrive on the destination for bridge routes; treat as guidance, not a promise.- Tool / route breakdown — which DEX or bridge brands participate, useful for power users auditing trust assumptions.
GaurdWallet renders these honestly — no fabricated exchange rates. If the countdown expires, fetch a fresh quote via /api/swap/quote before signing.
Always compare expected vs minimum received. A wide gap signals fees, impact, or long bridge paths. Learn the math in crypto slippage explained.
Same-chain vs cross-chain routes
Same-chain swaps route through DEX aggregators on one network — functionally similar to other swap routers, but accessed via LI.FI’s unified interface in GaurdWallet.
Cross-chain bridges change chain IDs. LI.FI selects among supported bridge protocols that match the token pair and amount. Some routes swap into a bridge-friendly asset first, then bridge, then optionally swap on destination — all bundled into the plan you preview.
This is why swap vs bridge matters conceptually even when the UI feels like one button.
| User intent | LI.FI may compose |
|---|---|
| USDC → DAI on Polygon | DEX swap only |
| USDC Polygon → USDC Base | Bridge (± minor swap legs) |
| ETH Arbitrum → USDC Optimism | Swap + bridge + swap |
Execution and multi-step flows
Simple swaps often need one signed transaction (plus prior ERC-20 approval). Complex bridge routes may require:
- Approval for ERC-20 spend (exact amount in GaurdWallet).
- Source-chain transaction initiating the bridge.
- Destination-side fulfillment — sometimes automatic via relayers, sometimes requiring an additional claim step depending on bridge design.
LI.FI encodes what the wallet should broadcast first. GaurdWallet requests transaction payloads through /api/swap/tx after you confirm a quote, then you sign in the non-custodial client.
Status monitoring after you sign
Bridges are asynchronous. After broadcast, LI.FI-compatible status endpoints track progress (source confirmation, relay, destination credit). GaurdWallet polls via /api/swap/status and surfaces a progress card on the Dashboard until completion or failure.
Do not submit duplicate bridges because a block explorer looks quiet — wait for status or verify the source transaction hash first.
GaurdWallet proxy architecture
LI.FI integrations typically require API keys. GaurdWallet keeps keys on the server and exposes narrow proxy routes:
/api/swap/quote— fetch routing quotes without embedding secrets in JavaScript./api/swap/tx— retrieve transaction data to sign./api/swap/status— monitor bridge lifecycle.
Proxies reduce key leakage risk but do not centralize custody: private keys remain on your device; the server never asks for your seed phrase. You remain responsible for verifying networks, spenders, and minimum received.
What LI.FI does not cover in GaurdWallet
- Solana swaps — handled by Jupiter, not LI.FI, in v0.2.1.
- BTC / LTC / TRON bridges — out of scope for Exchange in this release.
- Solana cross-chain — same-chain Jupiter swaps only.
For product steps and risk checklist, see how to swap and bridge and the swap & bridge hub. Ready to try a route? Open Exchange with a small test amount.
FAQ
Is LI.FI a bridge? It integrates many bridges; think “router of routers.”
Why do two quotes differ? Different paths, gas, bridge liquidity, and timing. Refresh if expired.
Does proxying quotes custodialize funds? No — it custodializes API access, not your keys or token balances.
Trust assumptions you still make
LI.FI selects among integrated protocols, but your signature approves specific contract calls. You trust that calldata matches the preview, that the bridge relayer will complete destination steps, and that token contracts behave as standard ERC-20. Aggregators reduce search cost; they do not eliminate smart-contract risk.
When comparing two quotes with similar minimum received, weigh execution duration, number of steps, and brand familiarity. Sometimes the faster route carries a newer bridge with shorter track record — a subjective trade only you can make.
Keep a personal log of successful routes (chain pair, asset, tool names) for repeat operations. GaurdWallet does not recommend routes; it displays what the API returns at quote time.
Reading the route tool breakdown
Power users should expand the tool list in the quote UI when available. Seeing “Uniswap V3 → Stargate” (names illustrative) tells you which protocols must stay online for the transfer to finish. If any step rhymes with a protocol you distrust, cancel and request a fresh quote — LI.FI may surface a different path seconds later.
Gas estimates on bridges are notoriously noisy during spikes. Budget extra native token on the source chain; running out of gas mid-bridge strand assets in protocol-specific states that may need support articles from the bridge vendor, not magic fixes from the wallet.
Status polling through /api/swap/status is the supported way to know when destination funds arrive. Block explorers alone can mislead if you watch only the source hash while relayers work on the far side.
When LI.FI routes fail or stall
Source transactions can succeed while destination fulfillment delays — not a wallet bug, but bridge operational risk. Status endpoints exist precisely because explorers on one chain do not show credits on another.
Quotes that revert often do so on slippage or stale calldata. Refresh, compare toAmountMin, and avoid raising tolerance without reading impact. Pair with crypto slippage explained when swap legs fail inside bridge routes.
If a route repeatedly selects a tool you distrust, try a different amount or time of day; aggregators re-query liquidity graphs on each quote. GaurdWallet displays outcomes, it does not manually curate routes per user.
Chain IDs and user-visible networks
LI.FI quotes are sensitive to correct chain identifiers. GaurdWallet maps human-readable network names to those IDs when requesting quotes. Picking the wrong From network is a common failure mode — the quote may succeed while your wallet holds no balance on that chain.
After a bridge, switch your wallet view to the destination network before panic-searching for funds. Credits land on the destination chain address that matches your same seed-derived account.
For corridor-specific walkthroughs (USDC, Base, Ethereum), follow the cluster articles listed on the swap & bridge hub as they publish.
When teaching someone their first bridge, have them screenshot the source tx hash and destination minimum received before signing — habits that matter when status cards take minutes to complete.
Open Exchange only after you can restate the From chain, To chain, and minimum received in your own words.