If you are moving from an exchange to your own wallet, a cross-chain route can avoid an unsupported token by choosing another usable hop; if no connected path exists, it cannot complete the move. The intermediate asset is a step in the route, not necessarily something you need to hold or choose yourself. The key is whether each swap and transfer in the route has a supported asset and enough liquidity.
A route only works when its hops connect
Think of a route as a chain of swaps and transfers, each requiring a usable market or bridge path. A token may exist on a network but still be unusable for a particular route if the service cannot transfer it across chains or there is no suitable pool to swap it.
For example, imagine your wallet has ETH on Ethereum and you want USDT on Mantle. If there is no direct path, a route could swap ETH for an asset that can be transferred, bridge that asset, then swap it for USDT on Mantle. If a proposed intermediate token has no usable pool or transfer path, the router can leave it out and look for another connected sequence.
This is similar to ordinary swap routing: Uniswap’s routing explanation describes paths that pass through intermediate tokens when that gives a usable route. A cross-chain route adds a transfer between networks, where the asset or its recognized representation must also be supported on the relevant legs.
Skipping a token can change the cost and result
Removing a hop does not automatically make a route cheaper. An alternative token may have thinner liquidity, so the swap can have more price impact; extra swaps also consume gas. The route’s quoted output reflects its proposed path, but market prices and available liquidity can change before transactions finish.
If your move starts from Mantle and the direct asset path is unavailable, a Mantle bridge route may use a different intermediate asset when the required transfer and swap legs exist. Check that the destination asset is the one you want and compare the quoted amount with the amount you expect. A token with the same ticker on two networks can be a different contract or representation, so the name alone is not enough to confirm they are interchangeable.
Check the destination before you approve
Before signing, confirm the source network, destination network, input asset, and expected output. Chainlink’s cross-chain transfer education explains why bridges need a mechanism such as destination liquidity or a corresponding token representation; a route cannot simply make an asset appear on a network where no supported transfer path exists.
If no route appears, try a different destination asset only if you are willing to receive it, or move the asset in a separate step through a path you trust. The answer changes when you specifically need to hold a particular token at the destination: then a convenient intermediate hop is fine, but the final swap and destination version must both be supported.