A cross-chain route that delivers a different asset has at least two steps: it must transfer value between networks and convert one token into another. If you are used to an exchange, think of it as a trade plus a withdrawal to a different network, except you authorize the transactions from your own wallet.
The useful distinctions are:
- A bridge usually carries the same asset, or a mapped representation of it, across networks.
- To receive a different asset, the route must add a swap before or after the transfer.
- A single quote can bundle the steps, but the token contracts, fees and liquidity still matter.
What happens when the asset stays the same?
A same-asset bridge transfers a token to another network, where you receive that token or its mapped representation. In a lock-and-mint design, the source token is held in a contract and a corresponding token is issued on the destination; in a burn-and-release design, the destination representation is burned before the source asset is released.
This is the best fit when you want to keep holding the same asset and use it on another network. A canonical bridge such as Mantle bridge is built for transfers between its connected networks and mapped assets. It does not turn a stablecoin into a different token just because you selected another destination.
Check the destination network and token contract, not only the ticker. Two tokens can share a symbol while representing different contracts or issuers, and an app on the destination network may accept one version but not another. Ethereum.org’s overview of bridges describes the broader distinction between native bridges and liquidity networks.
When does the route swap before or after bridging?
A route can swap on the source network, bridge the resulting asset, then optionally swap again after arrival. This suits you when the bridge supports a particular transfer asset but your destination app needs a different one; each swap needs a usable trading pool on the network where it happens.
For example, say you start with 100 USDT and the route swaps it into an asset the bridge can carry. The first swap might produce 99.5 units after its trading costs; after bridging, a destination swap might leave 98.8 units of the token you wanted. Those figures are illustrative: the actual output depends on the quote, pool depth, price movement and route fees.
Compare the final amount you will receive after every conversion, rather than comparing only the bridge fee. A swap can charge a pool fee and incur price impact—the change in execution price caused by the size of your trade—while each network transaction also needs gas. If the route requires a token approval, that is a separate source-network transaction and gas cost. For a practical comparison of where a conversion sits in the route, when to swap before a Mantle bridge is the fee question to weigh against the final output.
How does a liquidity route deliver a different asset?
A liquidity route can pay the destination asset from funds already available on that network, while settling the source-side transfer separately. A liquidity provider, sometimes called a solver or relayer, takes on the timing and inventory risk and is compensated through the quoted price or fee.
This is often best when you want one wallet-to-wallet route and a specific destination asset without arranging separate trades yourself. It may not fit if destination liquidity is thin: the quote can worsen, the available output can be limited, or the route may be unavailable. A bundled flow also does not mean there is only one transaction behind the scenes; you may still authorize source-side actions, and the destination payout depends on the route’s settlement design.
Before signing, read the quote as a trade instruction: confirm the source asset and network, destination asset and network, recipient wallet, minimum output and expiry or slippage setting. Slippage is the amount the execution price may move before the route fails or completes at a worse rate. Keep enough of each network’s gas token for the transactions you must authorize; a balance on the source network cannot pay fees on the destination.
Which route should you choose?
Choose a same-asset bridge when you want to hold that asset on another network and its mapped version suits your intended app. Choose a swap-before-or-after route when you have a clear destination token and can compare the combined trading and transfer costs.
Choose a liquidity route when its final output and settlement terms make sense for your trade. In your place, I would decide by the exact token contract the destination app accepts, then compare the estimated amount received after all steps—not by the number of actions shown in a quote.