Bungee Bridge routes token transfers across EVM chains and L2s. Use Bungee Bridge to compare routes for your source and destination tokens, then submit the chosen transfer from your wallet. A Bungee token bridge route may include swaps on either side, so check the destination token and expected output before signing.
How does Bungee Bridge move tokens between chains?
It finds a route through bridges and decentralized exchanges for the pair you specify. A route can swap your input token into a bridgeable asset on the source chain, transfer that asset across chains, then swap it into your requested token on the destination chain. If the bridge accepts your input token and delivers the token you want, those swaps are unnecessary.
Those stages explain why a confirmed source transaction is not proof of delivery: the bridge and any destination swap still have to complete. They also explain why two routes for the same token pair can differ in output, execution time and risk. Compare the full path, including the asset delivered, rather than treating every route as an equivalent transfer.
How do you complete a cross-chain transfer?
Choose the asset you need at the destination first, then work back to the token you hold. For example, if you hold 1,000 USDC on Ethereum and need USDC on Base, specify the intended Base token contract as well as its ticker; tokens with similar names can have different contracts.
-
Set the source and destination chains. Confirm that your wallet holds the input token on the source chain. Selecting the same wallet address as recipient is common, but specify the actual receiving address if the funds belong elsewhere.
-
Enter the input and output tokens and amount. Match each token by contract address where that matters, particularly for stablecoins with native and bridged versions. Keep enough of the source chain’s native token to pay for the transaction.
-
Compare the available routes. Check estimated destination output, route costs, expected time and whether a source or destination swap is involved. A faster liquidity route may deliver less than a slower route, so rank them by the amount you actually need to receive.
-
Review the quote and its execution bounds. Check the minimum output and any swap slippage setting before proceeding. As an illustration, 0.5% slippage on a 1,000-unit swap leg permits up to 5 units of price movement on that leg; it is not a statement of the transfer’s total cost.
-
Authorize the token spend if required. An ERC-20 route may need an allowance before the transfer transaction, while a route using a prior allowance or a signed permit may need fewer on-chain actions. The ERC-20 standard defines the approval mechanism; verify the spender and amount in your wallet.
-
Submit the transfer and track both chains. Save the source transaction hash, then check for completion at the destination before treating the transfer as finished. If delivery is delayed, that hash and the selected route identify the transfer you need to investigate.
Which route saves time or money?
The route with the largest quoted output is not always the one to choose: compare what you receive against the time and execution steps it requires. For a frequent transfer, the useful comparison is the whole transaction path, including any approval you must make this time.
-
Source gas: A new ERC-20 approval can add a transaction; an existing allowance can remove that step.
-
Swap impact: Thin liquidity can reduce output more than the bridge charge, especially for a large order.
-
Bridge cost and speed: Liquidity-backed delivery and other bridge mechanisms can have different prices and completion times.
-
Destination result: The received token contract and any final swap decide whether the funds are ready for your next action.
For the example 1,000 USDC transfer, I would first exclude routes delivering the wrong Base token, then compare net output and time among the remaining routes. Recheck a quote before signing if it has sat idle: DEX prices, available liquidity and gas conditions change. Ethereum.org’s gas documentation explains why the source transaction cost varies with gas used and the prevailing gas price.
What else should you know before transferring?
Check the final token, the full route cost and the destination result; those three checks resolve most practical questions before and after submission.
What does a transfer cost?
The cost depends on source gas, any approval, bridge charges and the price impact of swaps in the selected route. There is no reliable fixed amount for an Ethereum-to-Base transfer: gas and liquidity change, and a different token pair may require different swaps. Compare the input amount with the quoted destination amount in the same unit to judge the total effect.
Why has the source transaction confirmed but the token has not arrived?
Source confirmation shows that the first on-chain action succeeded; it does not establish that bridge delivery or a destination swap has finished. Check the destination chain and token contract, then trace the route using the saved source hash. Avoid submitting the same transfer again solely because the destination balance has not updated; a second submission can create a second transfer.
Do I need gas on both chains?
You need the native gas token on the source chain to submit an ordinary wallet transaction. A route may cover destination execution within its quoted cost, while another may require a separate destination action. Check the route’s required transactions before sending, especially if you plan to use the received token immediately and have no native token at the destination.
Set the exact destination asset, compare complete routes, and sign only after checking output and transaction requirements. Track delivery on the destination chain before starting the next transfer.