A cross-chain route is cheaper when its bridge charge, swap execution and gas together leave you with more usable destination tokens, provided you compare the same input, output and slippage limit. A “bridge fee” alone is not the total cost if the route also converts tokens.
- Separate bridge charges, swap fees, price impact and gas.
- Compare the final amount you can actually use.
- Choose where the swap happens based on depth, gas and execution risk.
How Mantle bridge funds an app depends on the destination asset and gas token the app needs. That choice changes which route costs are relevant: a same-token transfer has no swap leg, while a different destination token adds a market trade to the bridge.
Bridge the same asset when conversion is unnecessary
A bridge-only route transfers a supported asset across networks, so its main costs are the source transaction’s gas and the bridge’s fee model. Depending on the bridge, that model may include a relayer charge, liquidity or inventory cost, and destination gas; some bridges instead rely on proof and claim transactions, with the user paying for destination execution separately.
This option is best when the same asset is useful on both chains, such as moving USDC to an app that accepts USDC. It does not fit when the app requires another token: a later swap adds a separate transaction, gas cost and market exposure that a bridge-only quote does not include.
Bridge fees are route-specific, not a fixed percentage of every transfer. Liquidity-based relayers may price by token pair, pool utilization, size, destination gas and the cost of rebalancing funds. A protocol may display some of those costs as one net deduction from the output amount, so inspect the quote’s fee breakdown rather than assuming the displayed “bridge fee” includes every gas payment.
Swap before bridging when the source market is better
An origin-side swap converts the input on the source chain, then bridges the resulting asset. Its total includes source gas, the swap pool fee and price impact, plus the bridge charge and any destination gas not covered by the bridge.
This is best when the source chain has deeper liquidity for the conversion, or when the bridge accepts the desired destination asset as its input. It fits less well if the source-side token pair is thin, or if you must already hold a particular bridgeable asset and converting into it creates an unnecessary trade.
For example, someone holding ETH who needs USDC on another chain could swap to USDC before bridging if the source market offers a stronger net quote. But the comparison must account for the extra source-chain transaction; a low pool fee does not compensate for weak liquidity, high price impact or expensive source gas.
Bridge first and swap on the destination chain when its market wins
A destination-side swap transfers the bridge asset first and trades it into the required token after arrival. The full cost includes the bridge’s net deduction, destination swap fee and price impact, and destination gas for the trade.
This is best when the destination market is deeper or the app needs a token that is readily available there. It may not fit if destination gas is costly, the wallet lacks the chain’s gas token, or the bridge delivers an asset that has poor liquidity against the required output.
Swap fees are set by the pool or exchange route, and can vary substantially; concentrated-liquidity pools, for example, use different fee tiers. The fee is distinct from price impact: a trade can use a low-fee pool and still move the price against itself if its size is large relative to active liquidity. Check both the quoted output and its minimum after slippage protection.
Use a combined bridge-and-swap route when its net output wins
A composed route coordinates the bridge and one or more swaps so the destination receives the requested asset. It can execute a source swap, a destination swap, or both; an aggregator may present a single expected output even though the route contains several legs and fee sources.
This option is best when convenience and a single target output matter, and when its net quote beats manually comparing separate legs. It is a poor fit if the quote hides the breakdown, uses a weak pool, or sets slippage so tight that normal price movement causes execution failure. A destination swap can also fail after funds arrive if the minimum output cannot be met; understand whether the route refunds the unswapped asset and where that refund goes.
For a like-for-like comparison, use the same input size, destination token, recipient and slippage tolerance. Say a $1,000 transfer has an illustrative bridge cost of $2, a 0.05% swap fee ($0.50), 0.15% price impact ($1.50), and $1.10 in source and destination gas: the total is about $5.10, not $2. The percentages are examples, not a current quote; live costs depend on route, pool depth, gas prices and bridge liquidity.
At mantlebridge.us, readers can compare routes that bridge and swap across chains in one flow. For a Mantle bridge, compare the final destination amount and all included gas against a same-asset bridge plus a separate swap; choose the route that leaves the required token available with acceptable slippage and execution conditions.
Top comments (0)