A stablecoin bridge is a settlement event, not a transfer: the source ledger loses a token and the destination ledger gains one, so the destination mint decides the route. Once I read bridge quotes as settlement events, aggregators stopped being a black box: every route is a composition of mints, pools, and DEX legs, and the only hard rule is to know which mint produces the token that arrives.
Same-issuer mints and pool mints
The first sort is whether the arriving token comes from the stablecoin issuer’s own contract or from a pool owned by an intermediary. Same-issuer burn/mint is the clean product: source supply is burned, a message authorizes a mint on the destination chain, and the new token is what that chain’s native apps expect. There is no second redemption leg and no pool that can run dry. Its limit is availability: not every stablecoin has an issuer-run mint on every chain you need.
When the issuer does not run a mint, the bridge uses liquidity. A pool holds the stablecoin on the source side and a partner pool holds a token on the destination side, and the transfer is a matched withdrawal from the two pools. That is why a quote can show “USDC” on both ends and still be a worse outcome: the destination token can be a wrapper that redeems through the bridge operator. The market prices that wrapper based on what the operator’s custody is worth, and that price is not always $1.
The DEX legs between the mints
The third leg is optional DEX hops. A direct bridge quote can be expensive when the source pool is thin, so an aggregator sells the source stablecoin into a liquid intermediate, bridges that, and buys the destination stablecoin back on the far side. The first hop may fill from a Uniswap Protocol pool; the final hop may source the token through a 0x Protocol order book. Arbitrum One is the realistic case: it runs its own ledger and its own token contracts, so “USDC” there is a distinct contract from “USDC” on Ethereum, and a bridge has to change that contract.
The extra legs are a trade-off, not a free lunch. Each hop adds price risk and another transaction to fail, and the aggregated quote is only as honest as the liquidity it can see. The reason to take the route is simple: the total output after slippage and bridge fees can be higher than a direct bridge that needs a thin or one-sided pool.
What a route aggregator actually does
An aggregator such as Paraswap makes this legible: it quotes the bridge and the DEX hops as one route, so you see the total output instead of a disconnected list of steps. The same pair can have three viable routes with three different destination contracts, and the quote has to be read with the destination form in view. Try the same pair at ameblo.jp.
That is the decision rule: when the issuer’s own mint exists and the total output is within reach, take it; when it does not, the aggregated pool route is the practical way to move the value, and you take the wrapper’s redemption risk knowingly. The rule is not “avoid wrappers”; it is “know which wrapper you are holding before you sign the quote.”
FAQ
How do I tell whether the destination stablecoin is native or a wrapper? Compare the destination contract against the stablecoin issuer’s published contracts on that chain; an aggregator shows the contract address in the route, and if it is not the issuer’s, it is a representation.
Is it ever worth taking a wrapper route when a native route exists? Only when the native route’s slippage and fee leave you with less output than the wrapper route by more than the wrapper discount, and even then only if you can exit the wrapper without holding it.
Why do aggregators add DEX hops instead of bridging directly? Because the direct pool may be thin or one-sided, and a two-hop route through a liquid intermediate can settle with a lower total cost once both quotes are combined.
What is the biggest mistake in reading a bridge quote? Treating any token named USDC or USDT as the same asset; the destination chain is a separate ledger, and the name is not the contract.