01
Connect your wallet & select chains
Connect a non-custodial wallet (MetaMask, Rabby, WalletConnect). Choose the source chain and destination chain — Jumper supports 30+ EVM and non-EVM networks.
- What is Jumper Exchange and how does Li.Fi aggregation work
- Supported chains, networks, and tokens
- Jumper Exchange fees: bridge fees, swap fees & gas explained
- How Jumper picks the best cross-chain route
- How to use Jumper Exchange: step-by-step tutorial
- Slippage on Jumper: what it is and how to set it correctly
- Is Jumper Exchange safe? Bridge & smart-contract risk analysis
- Jumper vs other bridge aggregators: key trade-offs
- Best practices: how to bridge assets without costly mistakes
- Troubleshooting: stuck transactions, missing funds, failed bridges
- Authoritative sources & references
- FAQ
What Is Jumper Exchange and How Does Li.Fi Aggregation Work?
Jumper Exchange is the consumer-facing interface built on the Li.Fi protocol — a cross-chain liquidity infrastructure that aggregates bridges, DEX aggregators, and on-chain swap routers into a single routing engine. Instead of manually choosing between Stargate, Hop, Across, Connext, or Celer for every transfer, Jumper queries them all simultaneously and returns the best available path.
A single Jumper transaction can combine multiple steps: a swap on a DEX on the source chain, a bridge to the destination chain, and a second swap into the target token — all in one user-approved transaction flow. This multi-hop routing is what distinguishes Jumper from single-bridge tools.
For casual users
Move tokens between chains without researching individual bridges. Get a competitive rate and a simple UI with real-time route comparison.
Simple UXNo research needed30+ chains
For power users
Full route transparency — see which bridge and which DEX is being used, estimated gas on each chain, bridge finality time, and per-step fee breakdown.
Route detailsCustom slippageAdvanced mode
Li.Fi vs Jumper: Li.Fi is the underlying protocol and API used by developers.
Jumper is the polished end-user product. Same routing engine, different audience.
Jumper Exchange Supported Chains, Networks, and Tokens
Jumper supports a broad and growing list of EVM-compatible networks as well as select non-EVM chains. Supported networks include but are not limited to:
Ethereum
Arbitrum
Optimism
Base
Polygon
BNB Chain
Avalanche
zkSync Era
Linea
Scroll
Gnosis
Fantom
Solana
+ more
Token coverage is broad — most major stablecoins (USDC, USDT, DAI), native gas tokens (ETH, BNB, MATIC), and hundreds of ERC-20s are supported. Token availability on a specific bridge route depends on which bridges support that token pair, which Jumper surfaces automatically.
Check before bridging: Not every token is available on every chain via every bridge.
Always verify the specific route and token is supported on the Jumper interface before expecting a route to exist.
Jumper Exchange Fees: Bridge Fees, Swap Fees, and Gas — What You Actually Pay
Understanding the full cost of a Jumper transaction requires separating four distinct fee components. Many users are surprised by the total cost because they only account for the bridge fee.
| Fee type | Who charges it | Typical range | Avoidable? |
|---|---|---|---|
| Bridge protocol fee | Underlying bridge (e.g. Stargate, Hop) | 0.01% – 0.1% | Varies by route |
| DEX swap fee | DEX used for source/dest swap | 0.01% – 0.3% | Choose direct bridge if possible |
| Source chain gas | Source network validators | Varies widely | Time transactions off-peak |
| Destination chain gas | Destination network validators | Often sponsored or low | L2s are much cheaper |
| Li.Fi / Jumper fee | Li.Fi protocol | Small % on certain routes | Built into route |
Real total cost: Always look at the "You receive" output on the Jumper UI — that figure
already deducts all fees except destination gas. The difference between your input and that output
is your true all-in cost of the bridge + swap.
How Jumper Finds the Best Cross-Chain Route: Speed, Cost, and Output Trade-offs
Jumper's routing engine (Li.Fi) queries dozens of bridges and DEX aggregators in parallel and ranks returned routes by three main dimensions:
Optimise for output (default)
Maximises the token amount received on the destination chain. May use slower bridges or more complex multi-hop paths if they yield more tokens after fees.
Optimise for speed
Prioritises the fastest finality time. Some bridges settle in minutes; others require 15–30+ minutes for Ethereum finalisation. Speed routes may cost more.
Each displayed route shows the bridge used, any intermediate DEX swap, estimated time to completion, total fees, and the final received amount. Jumper makes this data visible so users can make an informed trade-off rather than blindly accepting the first result.
Route freshness: Routes are quoted in real-time but prices and availability shift.
If you wait several minutes before confirming, refresh the route to avoid stale price data and potential failed transactions.
How to Use Jumper Exchange: Step-by-Step Bridging Tutorial
- Go to the official Jumper Exchange URL — always use a bookmarked link. Confirm the URL in your browser before connecting your wallet.
- Connect a non-custodial wallet — MetaMask, Rabby, WalletConnect, or Coinbase Wallet are all supported. Use a hardware wallet for large amounts.
- Select source chain and token — choose the chain you're sending from and the token you want to bridge or swap.
- Select destination chain and token — this is the chain and token you want to receive. These can be different tokens (bridge + swap in one step).
- Enter the amount and review available routes — compare routes by output amount, fees, and speed. Select the route that fits your needs.
- Check slippage tolerance — default slippage is usually 0.5–1%. For volatile tokens or low-liquidity routes, you may need to adjust.
- Confirm and sign the transaction in your wallet — verify the contract address and transaction details before signing.
- Track the transaction — Jumper provides a tracking link. For cross-chain transactions, finality can take from a few minutes to 30+ minutes depending on the bridge.
Before any large bridge: test with a small amount first. Cross-chain transactions are irreversible.
A $2 test costs little; a failed $10,000 bridge is a much larger problem.
Slippage on Jumper Exchange: What It Means and How to Set It Correctly
Slippage is the difference between the expected output when you submit a transaction and the actual output when it executes. On cross-chain swaps, slippage can occur at the source DEX, the destination DEX, or both.
| Scenario | Recommended slippage | Reason |
|---|---|---|
| Stablecoin ↔ Stablecoin bridge | 0.1% – 0.3% | Tight liquidity, predictable price |
| ETH or large-cap token | 0.3% – 0.5% | Good liquidity across routes |
| Mid/small-cap token swap | 0.5% – 1.5% | Lower liquidity, more price impact |
| Congested network / peak gas | 1% – 2% | Transaction may take longer to settle |
Don't set slippage too high: Very high slippage (5%+) makes your transaction vulnerable
to MEV sandwich attacks, where bots front-run your swap and extract the gap between your expected
and maximum-acceptable price.
Is Jumper Exchange Safe? Bridge Risk, Smart-Contract Risk, and What Can Go Wrong
Jumper Exchange is built on Li.Fi, a protocol with a track record and multiple security audits. But aggregating bridges means aggregating their individual risk surfaces. Every bridge in the route is a separate smart-contract system.
| Risk | Severity | Mitigation |
|---|---|---|
| Smart-contract exploit (bridge) | Medium-High | Li.Fi audits + bridge-level audits; use well-established routes |
| Stuck / pending transaction | Medium | Jumper's built-in refund mechanism; allow sufficient time |
| Wrong destination chain/token | High (user error) | Double-check chain and token before confirming — irreversible |
| Phishing / fake Jumper site | High (user-controlled) | Bookmark official URL; verify domain before connecting wallet |
| Liquidity crunch on bridge | Low-Medium | Jumper shows available liquidity per route; choose routes with depth |
| MEV / sandwich attack on swap | Medium | Use reasonable slippage (≤1%); avoid very high slippage tolerance |
Historical note: Li.Fi experienced a smart-contract exploit in 2024 affecting certain
token approvals. The protocol responded with patches and improved approval management.
Always revoke stale token approvals after bridging via any DeFi protocol.
Jumper Exchange vs Other Bridge Aggregators: Key Trade-offs
| Feature | Jumper (Li.Fi) | Socket (Bungee) | Rango Exchange | Direct bridge |
|---|---|---|---|---|
| Route aggregation | Yes — 20+ bridges | Yes — multiple bridges | Yes — broad coverage | No — single bridge |
| Swap + bridge in one step | Yes | Yes | Yes | Rarely |
| Non-EVM support | Solana + others | Limited | Broad | Depends |
| UI clarity | Clean, modern | Good | More complex | Usually simple |
| Smart-contract risk | Aggregator + bridge | Aggregator + bridge | Aggregator + bridge | Bridge only |
When to use a direct bridge instead: If you're doing a very large transfer on a
well-established route (e.g. ETH → Arbitrum via Arbitrum's native bridge), using the official
bridge directly reduces aggregator risk and is often the most trust-minimised option.
Best Practices for Bridging with Jumper Exchange: How to Avoid Costly Mistakes
- Always bookmark the official Jumper URL and check the domain before connecting your wallet — phishing sites are the most common cause of fund loss.
- Start with a small test transaction on any new route or token pair, especially on routes you haven't used before.
- Verify the destination chain and token match what you intend — cross-chain errors are irreversible.
- Keep slippage reasonable — 0.3–1% for most transactions. Avoid high slippage settings that expose you to MEV.
- Maintain gas on the destination chain — some bridges require a small gas payment to claim on arrival. Having zero gas on the destination can leave you unable to use received tokens.
- Revoke token approvals after bridging — unlimited approvals on bridge contracts are a security risk. Use Revoke.cash periodically.
- Use a hardware wallet for meaningful amounts — software wallets are significantly more vulnerable to phishing and malware.
- Don't rush during high-network congestion — gas spikes can make a bridge unexpectedly expensive. Wait for gas to normalise for non-urgent transfers.
Jumper Exchange Troubleshooting: Stuck Transactions, Missing Funds & Failed Bridges
"Transaction is pending / stuck for a long time"
- Some bridges (especially those finalising on Ethereum mainnet) take 15–40 minutes. Check the estimated time shown when you selected the route.
- Use Jumper's built-in transaction tracker — it shows which step the bridge is currently at.
- If a transaction is genuinely stuck beyond the estimated time, Li.Fi offers a refund/recovery mechanism from the transaction history page.
"Tokens arrived on wrong chain" or "I can't find my tokens"
- Confirm you have the destination chain added to your wallet and are viewing it. Many users forget to switch network in MetaMask after bridging.
- Some tokens bridged via non-canonical bridges arrive as wrapped versions — add the wrapped token contract address to your wallet manually.
- Check the destination chain block explorer using your wallet address to confirm whether tokens arrived on-chain, regardless of what the UI shows.
"Transaction failed / reverted"
- Insufficient gas is the most common cause — ensure you have enough native token on the source chain to cover both the bridge and the gas fee.
- Slippage exceeded tolerance — the market moved while your transaction was pending. Increase slippage slightly and retry.
- Route became unavailable after you confirmed — bridge liquidity was depleted. Refresh routes and select an alternative.
Always verify on-chain first — the Jumper UI can lag or display stale states.
Use the source and destination chain block explorers to confirm the true status of your funds.
Jumper Exchange: Authoritative References & External Sources
Jumper Exchange & Li.Fi Protocol
- Jumper Exchange — Official Website
- Li.Fi Protocol — Official Site
- Li.Fi — Technical Documentation
- Li.Fi — Smart Contracts & Source Code (GitHub)
Cross-Chain Bridge Safety & Education
- Ethereum.org — Bridges Overview
- Chainalysis — Blockchain Security Research
- Rekt News — DeFi Exploit Post-Mortems
Security Hygiene & Smart Contract Safety
- Revoke.cash — Token Approval Manager
- Ethereum.org — How to Revoke Token Access
- OpenZeppelin — Smart Contract Security Audits
DeFi Data & Analytics
About: Prepared by Crypto Finance Experts as a practical, SEO-oriented knowledge base
for Jumper Exchange: cross-chain routing, fees, slippage, supported chains, security, comparisons, and troubleshooting.
Jumper Exchange: Frequently Asked Questions
Jumper Exchange is a cross-chain bridge and swap aggregator powered by the Li.Fi protocol. Unlike a single bridge (which only connects two specific chains), Jumper queries 20+ bridges and DEX aggregators simultaneously, finds the best route, and can execute a bridge + swap in a single flow. You get better prices and more route options without manually comparing each bridge.
The total cost of a Jumper transaction includes: the underlying bridge protocol fee (typically 0.01–0.1%), any DEX swap fees if a cross-chain token swap is involved, gas on the source chain, and often a small Li.Fi/Jumper protocol fee on certain routes. The "You receive" number in the Jumper UI already reflects all fees except destination gas — use it as your real cost reference.
Jumper supports 30+ chains including Ethereum, Arbitrum, Optimism, Base, Polygon, BNB Chain, Avalanche, zkSync Era, Linea, Scroll, Solana, and more. The list expands regularly as Li.Fi adds new bridge integrations. Always check the current Jumper interface for the latest supported networks.
Bridge times vary by route. Optimistic rollup bridges to/from Ethereum mainnet (native exits) can take 7 days. Third-party bridges like Stargate or Hop typically settle in 1–15 minutes. Jumper shows the estimated time per route before you confirm, so you can choose speed vs. cost accordingly.
Jumper is built on the audited Li.Fi protocol and has been used for billions in cross-chain volume. However, every bridge it aggregates is a separate smart-contract system with its own risk profile. The main user-controlled risks are phishing (always verify the URL), wrong destination chain, and excessive token approvals. Treat cross-chain bridging as a higher-risk DeFi operation and always test new routes with small amounts first.
First, check if the bridge's estimated time has actually elapsed — many users worry too early. Check on-chain using the source chain block explorer. If the transaction is genuinely stuck past the estimated time, use Li.Fi's transaction recovery tool accessible from the Jumper transaction history. For bridges that support refunds, you can reclaim tokens on the source chain if the bridge failed to deliver.
For stablecoin-to-stablecoin bridges, 0.1–0.3% is typically sufficient. For ETH or large-cap tokens, 0.3–0.5% covers normal market movement. For smaller-cap tokens or congested markets, 0.5–1.5% may be needed. Avoid setting slippage above 2–3% as it increases your vulnerability to MEV sandwich attacks, where bots extract profit from the gap between your expected and maximum-acceptable price.
Li.Fi, the protocol underlying Jumper, has explored tokenisation and incentive programs. Check the official Jumper and Li.Fi sites for the most current information on any rewards, referral programs, or token-related features, as these change over time and are not covered by this guide's static content.
Jumper Exchange is primarily focused on fungible token bridging and cross-chain swaps. NFT bridging is a separate use case handled by dedicated NFT bridge protocols (such as LayerZero-based NFT bridges). For fungible ERC-20 tokens and native gas tokens, Jumper provides excellent coverage across supported chains.