Bungee bridge is a cross-chain route aggregator that compares bridges and liquidity sources so you can transfer or swap assets between networks through one planned flow. The route that matters is the one that delivers an acceptable amount in an acceptable time after fees, slippage and required transactions. To use it, set the transfer, compare quotes, check the minimum received, submit the source transaction and verify delivery.
Key points
- A route can include a source swap, a bridge transfer and a destination swap.
- Compare net output and required transactions alongside estimated time.
- A confirmed source transaction does not mean the destination transfer is complete.
What does the route aggregator actually provide?
It provides routes for a specified input asset and amount on one chain to an output asset on another. Each quote reflects available bridges and liquidity for that pair at that moment, with an estimated receipt and execution path. The selected bridge performs the cross-chain leg; the aggregator finds and presents the route.
The choice is more precise than selecting two networks. A quote for USDC on Ethereum to USDC on Arbitrum can differ from one for ETH to USDC across the same chains because the latter needs a swap somewhere in the path. Bungee Manual exposes multiple routes for comparison when available, while an automatically selected route reduces the choice the user must make.
Supported networks are only the first filter. Token contracts, transfer direction, amount and available liquidity determine whether a usable quote appears. A token with the same ticker on two chains is not necessarily the same asset, so check the destination token contract and the receiving address before treating a route as equivalent.
How does a cross-chain route execute?
A route turns your source asset into an asset the underlying bridge can move, transfers value across chains, then delivers the requested destination asset. If the source asset is already suitable for that bridge, the source swap disappears; if the destination asset differs, a destination swap may be part of settlement. The quote’s route details tell you which operations are included.
For an ERC-20 input, execution may start with an allowance transaction or a Permit2 signature, depending on the route and approvals you already have. You then submit the source-chain transaction. Once it confirms, the bridge or its liquidity provider must complete the destination leg; source confirmation alone is not proof that the recipient has been paid.
This distinction matters when comparing “one transaction” routes. One wallet transaction can initiate a source swap and bridge transfer together, while destination execution still happens later. A route that requires a separate claim or destination transaction may leave you needing native gas on the receiving chain.
Which quote is faster or cheaper in practice?
Compare routes using the same input amount, destination token and recipient. The number to optimize is the amount that reaches the recipient within a time you can tolerate. Check these four entries in each quote:
- Estimated output: the projected destination-token amount at the quoted rate.
- Minimum received: the amount protected by the route’s slippage terms, where shown.
- Execution costs: source gas, bridge or liquidity fees, swap price impact and any displayed service fee.
- Steps and time: approvals, source transactions, possible claims and estimated completion time.
A bridge fee by itself cannot rank those routes. In Bungee Auto, the Bungee bridge quote is useful because it places the expected receipt beside the route’s execution details. Bungee’s documentation says it adds no separate user fee, although an integration may charge one; the underlying route still has costs.
Consider an illustrative 1,000 USDC transfer from Ethereum to Arbitrum. Route A quotes 996 USDC in about 20 minutes; route B quotes 994 USDC in about two minutes. The decision is whether the extra 2 USDC is worth the estimated wait, after checking that both figures include comparable fees and that neither route adds a claim transaction.
Slippage can change that comparison. With an illustrative 0.5% tolerance, a 996 USDC quote could permit a receipt near 991 USDC if that tolerance applies to the quoted output; inspect the actual displayed minimum rather than calculating it from a headline rate. A tighter tolerance protects the floor but can make a swap fail when prices move before execution.
What are the five steps to complete a transfer?
Complete the transfer by fixing the exact asset pair first, then checking the route immediately before signing. Quotes can change with liquidity, gas prices and bridge capacity, so a saved comparison is only a starting point.
- Set the pair. Choose the source and destination chains, token contracts, input amount and recipient. Ethereum uses chain ID 1 and Arbitrum uses 42161; 1,000 USDC is commonly represented as 1,000,000,000 base units because USDC has six decimals.
- Read the routes. Compare estimated and minimum output, time, fees and the underlying bridge. If no quote appears, try a different amount or output asset rather than assuming the network itself is unsupported.
- Check the wallet actions. Confirm the source wallet has enough native token for gas and see whether the route requires an ERC-20 approval. An existing allowance can remove that extra on-chain step.
- Submit the source transaction. Check the spender, amount, recipient and minimum receipt in the wallet prompt before signing. Keep the source transaction hash or request identifier.
- Track settlement. Follow the transfer status through source confirmation and destination completion, then verify the destination transaction and token balance in the recipient wallet.
For a large transfer or an unfamiliar token, a small test transfer can expose a wrong token contract or unsupported receiving address. Do not submit the full amount again while the first transfer is pending; resolve its status first.
Can I swap tokens while using the Bungee bridge?
Yes. The input and output tokens can differ, provided a route has liquidity for the required swaps and cross-chain transfer. For example, a route can take ETH on Ethereum and deliver USDC on Arbitrum, with the bridge carrying an intermediate asset between the two swaps.
Inspect where each swap occurs because it changes price impact, gas use and what happens if the destination leg cannot execute. A liquid direct bridge route may beat a swap-heavy route for same-token transfers, while the combined route may save steps when you need a different token at the destination.
Why is my Bungee bridge transfer pending?
A transfer can remain pending while the source transaction waits for confirmation, while the underlying bridge waits for finality or liquidity, or while the destination transaction is being executed. First check whether the source transaction succeeded, then look for a destination transaction hash in the transfer status. An estimated arrival time is not a settlement guarantee.
If the source succeeded but no destination transaction appears after the route’s expected window, use the saved hash or request identifier to inspect the underlying bridge status. Follow any claim or refund action shown for that route; if none appears, provide the identifier to support. If the destination transaction succeeded, verify the recipient and token contract before assuming the funds are missing.
Choose the route whose minimum acceptable receipt and completion time still make sense after every required transaction is counted.