Enter your transfer details
Select your source chain, destination chain, token, and amount. Bungee instantly passes these parameters to Socket Protocol's routing engine, which queries every integrated bridge and DEX aggregator simultaneously.
The complete guide to Bungee Exchange — a cross-chain bridge aggregator powered by Socket Protocol that scans 20+ bridges and DEX routes simultaneously to find you the fastest, cheapest, or highest-output cross-chain transfer. Understand how Bungee's intelligent route selection works, what the Refuel feature does for gas-less destination chains, how fees are calculated, which 30+ chains and tokens are supported, and how to use Bungee safely while avoiding the common pitfalls of cross-chain transactions.
Select your source chain, destination chain, token, and amount. Bungee instantly passes these parameters to Socket Protocol's routing engine, which queries every integrated bridge and DEX aggregator simultaneously.
Within seconds, Bungee displays all available routes ranked by your selected priority — maximum output (most tokens received), minimum time, or balanced best route. Each route shows the exact output, fee breakdown, bridge used, and estimated settlement time.
Choose your preferred route, review the full fee and output summary, approve token spending if needed, and confirm the bridge transaction. Bungee handles the entire routing — you interact with one interface regardless of which bridge executes the transfer.
Bungee's built-in transfer tracker shows real-time status across the bridge lifecycle. Once the route completes, tokens arrive on the destination chain — no manual claiming on most routes.
Bungee Exchange is the consumer product built on top of Socket Protocol — an interoperability infrastructure layer that aggregates bridges, DEXs, and cross-chain messaging systems into a unified routing API. Socket provides the back-end intelligence; Bungee provides the clean, user-focused front-end interface.
The problem Bungee solves is fragmentation: there are 20+ bridges operating across 30+ chains, each with different fees, speeds, security models, and token coverage. No single bridge is optimal for every transfer. Bungee queries all of them simultaneously and surfaces the best options for your specific transfer — turning a complex multi-protocol research task into a two-click operation.
Move tokens between chains without researching individual bridges. Get the best available rate, see exactly what you'll receive, and complete the transfer through a single interface regardless of which bridge executes under the hood.
Full route transparency — see exactly which bridge, DEX, and intermediate steps are used. Compare routes by output, speed, and fee breakdown. Advanced mode exposes the full Socket Protocol routing stack for manual route selection.
Bungee's routing intelligence is powered by Socket Protocol's routing engine, which evaluates routes across three dimensions simultaneously — allowing you to optimise for what matters most to your specific transfer.
| Optimisation mode | What it prioritises | Best for |
|---|---|---|
| Max output | Highest tokens received on destination — minimises total fee drag | Large transfers where a 0.1% output difference is meaningful in USD |
| Fastest route | Lowest estimated settlement time — may sacrifice some output | Time-sensitive transfers, high-volatility markets, urgent DeFi needs |
| Recommended (balanced) | Best risk-adjusted combination of output, speed, and route reliability | Most everyday transfers — default starting point for most users |
Bungee's routing also factors in bridge-specific considerations invisible to manual comparison: current liquidity depth per route, recent bridge performance and uptime, and whether a route requires token approval steps that add gas overhead. Routes that look similar on paper may differ significantly in practice — Bungee's real-time data surfaces these differences.
One of the most common friction points in cross-chain DeFi is arriving on a new chain with tokens but no native gas to interact with them. Bungee's Refuel feature solves this in a single step — letting you receive a small amount of destination chain native gas alongside your transfer, without visiting a CEX or a separate faucet.
During any Bungee transfer, enable Refuel to specify a small amount of native destination gas (e.g. ETH on Arbitrum, MATIC on Polygon, BNB on BSC) to receive alongside your bridged tokens. The gas cost is covered from your source chain assets — no destination wallet needed before bridging.
Use Refuel when bridging to a chain where you hold zero native gas — enabling you to immediately interact with received tokens without a separate gas acquisition step. Particularly useful for new chain exploration, airdrop collection, or onboarding users new to a specific network.
Bungee supports 30+ chains through Socket Protocol's integrated bridge and DEX network, covering all major EVM networks and expanding to non-EVM chains.
Token coverage is broad — USDC, USDT, ETH, WBTC, MATIC, BNB, AVAX, and hundreds of ERC-20 tokens are supported. Specific token availability per route depends on which integrated bridge supports that token on the selected chain pair.
| Fee component | Who charges it | Notes |
|---|---|---|
| Bridge protocol fee | Underlying bridge (Stargate, Hop, etc.) | Varies per bridge — Bungee shows you which bridge charges what |
| DEX swap fee | DEX used if a swap step is included | Only applies on routes requiring a token swap alongside bridging |
| Source chain gas | Source network validators | Ethereum mainnet highest; L2 source chains significantly cheaper |
| Destination gas | Destination network (often sponsored) | Many routes sponsor destination gas; check per-route details |
| Bungee / Socket fee | Socket Protocol | Small aggregator fee on certain routes; shown transparently in breakdown |
| Risk | Level | Mitigation |
|---|---|---|
| Underlying bridge exploit | Medium | Bungee routes through audited bridges; aggregating risk means a single bridge exploit can affect Bungee routes using it |
| Socket Protocol smart-contract risk | Medium | Socket has been audited; its contracts are a separate surface from individual bridges |
| Wrong destination chain or address | High (user error) | Irreversible — triple-check destination chain and address before confirming any transfer |
| Stale route execution | Low-Medium | Refresh routes if you wait more than a few minutes before confirming — prices and availability shift |
| Unlimited token approvals | Medium | Use exact-amount approvals where possible; revoke stale approvals via Revoke.cash after transfers |
| Phishing / fake Bungee sites | High (user-controlled) | Bookmark official Bungee URL; verify domain every session before connecting wallet |
Socket Protocol is the interoperability infrastructure that powers Bungee's routing engine. While Bungee is the consumer-facing product, Socket is the developer-facing API and SDK used by other projects to embed cross-chain bridging into their own interfaces.
Socket aggregates 20+ bridges into a unified routing API. Projects like Zerion, Rainbow Wallet, and other DeFi front-ends embed Socket's routing to offer bridging without building their own bridge integration infrastructure. Bungee is Socket's own first-party consumer product.
Bungee is to Socket what Jumper Exchange is to Li.Fi — the same routing engine, presented through a polished consumer interface designed for non-developer users. Both offer identical routing quality; Bungee adds a more visual, user-friendly experience on top.
| Feature | Bungee (Socket) | Jumper (Li.Fi) | Rango | Direct bridge |
|---|---|---|---|---|
| Underlying protocol | Socket Protocol | Li.Fi Protocol | Rango Protocol | N/A — single bridge |
| Bridge coverage | 20+ bridges | 20+ bridges | Broad multi-chain | Single bridge only |
| Refuel / gas drop | Yes — native Refuel feature | Limited | Limited | No |
| Cross-token swaps | Yes — bridge + swap in one | Yes | Yes | Rarely |
| Non-EVM chain support | Primarily EVM | Solana + others | Broadest non-EVM | Varies |
| Smart-contract track record | 2024 exploit (patched) | 2024 exploit (patched) | No major incidents | Bridge-dependent |
| Developer API | Socket API (widely used) | Li.Fi API | Rango API | No |
Bungee Exchange is a cross-chain bridge aggregator — it doesn't operate its own bridge, but instead queries 20+ existing bridges simultaneously and shows you all available routes ranked by output, speed, or a balance of both. A regular bridge gives you one option; Bungee gives you all options and helps you pick the best one. It's powered by Socket Protocol, the same interoperability infrastructure used by wallets and DeFi apps that embed bridge functionality.
Refuel lets you receive a small amount of native destination chain gas alongside your bridged tokens — paid from your source chain assets. Use it whenever you're bridging to a chain where you have zero or very low native gas. Without Refuel, you'd be stuck unable to use your bridged tokens without first acquiring gas through a CEX or faucet. Refuel caps the gas amount to prevent misuse — it's enough for several transactions, not unlimited gas.
Bungee queries all integrated bridges simultaneously via Socket Protocol and ranks the returned routes by your selected optimisation priority: maximum output (most tokens received), fastest settlement, or a balanced recommendation. Each route is evaluated on real-time parameters including current bridge liquidity, fee rates, settlement speed, and route reliability. You see all options and choose — Bungee doesn't make the final decision for you.
Bungee charges a small aggregator fee on certain routes (shown transparently in the fee breakdown). The main costs are the underlying bridge protocol fees (charged by Stargate, Hop, Across, etc.) and source chain gas. On many routes, Bungee's aggregator fee is offset by finding a more efficient bridge route than you'd find manually — meaning the total cost via Bungee is comparable to or lower than going directly to an individual bridge.
Socket Protocol experienced an exploit in January 2024 where attackers drained funds from users who had granted unlimited token approvals to Socket contracts — totalling several million dollars. The vulnerability was patched and Socket improved its approval architecture. The key lesson: never grant unlimited approvals to any bridge or aggregator contract. Use exact-amount approvals and revoke stale permissions via Revoke.cash after each session. The protocol has operated without a repeat incident since the patch.
Yes — Bungee supports cross-token bridging in a single step. You can bridge USDC on Ethereum and receive ETH on Arbitrum, for example, without manually doing a separate DEX swap on either end. Routes that include a swap step show the DEX used and any additional swap fee in the route breakdown. These multi-step routes are especially useful when you need a specific token on a specific chain and want to minimise wallet interactions.
Transfer times vary by the underlying bridge route selected. Fast routes (Across, Hop, Hyphen) typically settle in 1–5 minutes. Standard routes (Stargate, cBridge) settle in 5–15 minutes. Routes involving Ethereum mainnet finalisation can take 20+ minutes. Bungee displays the estimated settlement time per route before you confirm — if speed is critical, select the "Fastest" optimisation mode to prioritise low-latency routes.
Both are bridge aggregators but built on different protocols: Bungee runs on Socket Protocol; Jumper runs on Li.Fi. Routing quality is comparable for most common routes. Bungee's standout feature is its native Refuel (gas drop) implementation. Li.Fi/Jumper has broader non-EVM chain coverage (including Solana). Both experienced smart-contract exploits in 2024 and have since patched them. Use Bungee when Refuel is needed; use Jumper for Solana or other non-EVM routes where Bungee has limited coverage.
First, verify the source chain transaction on a block explorer — if it's unconfirmed, the bridge hasn't started and the issue is gas on the source chain, not Bungee. If the source transaction confirmed, check your transfer in Bungee's transfer history with the transaction hash for current status. If it's genuinely stuck beyond the estimated time, look for a refund or recovery option in the transfer history. Contact Bungee support via official channels with your transaction hash — never share your seed phrase with any support contact.