Before sending funds, check that the destination chain can deliver the exact token your app accepts, by contract address as well as by name. A matching ticker does not prove that two tokens are the same asset: USDC, for example, can have different contracts on different networks. If you choose a route that swaps on arrival, check the output token too.
Compatibility depends on the destination contract and route
A bridge can offer a route only when its transfer method can deliver an asset the destination network and route support. The screen may filter out tokens that have no supported destination version, no usable transfer path, or no route for the requested swap. The exact checks vary by bridge service.
For a Mantle bridge transfer, start by identifying the token contract on the chain where you will use it. When you want to bridge and swap in one flow, the Mantle bridge swap service is an option for moving assets across supported networks and swapping during that transfer. Confirm the destination asset against the app’s accepted token before choosing a route.
Compatibility usually turns on a few concrete details:
- Destination chain: the route must deliver to the network where the app runs.
- Token contract: the destination token needs the correct contract, not merely a familiar symbol.
- Transfer method: the bridge must support the token’s route, such as releasing or minting its destination representation.
- Swap output: if the route converts the asset, its final token must be accepted by the app.
Decimals matter when you compare amounts. For example, 100 USDC in a six-decimal token is represented as 100,000,000 base units; a token with different decimals uses a different on-chain amount for the same human-readable balance. A route should account for this conversion, but checking the destination contract helps catch lookalike tokens that a symbol search can miss.
Verify the output before committing the transfer
Check the destination chain, token contract, and quoted output as one route; each affects whether the funds will be usable for your task. Use this sequence before sending:
- Open the app’s deposit or swap details. Find the destination network and the token it accepts. Copy the contract address from the app’s trusted token information if it provides one.
- Choose the destination network. Make sure it is the same network the app uses; a token on another chain will not meet that requirement even if its ticker matches.
- Select the intended output token. Compare its contract address with the app’s accepted token. If you are bridging without a swap, check the bridged representation the route delivers.
- Read the route quote. Check the estimated output amount and whether the transfer includes a swap. For instance, if you send 100 USDC and the quote estimates 99.4 USDC after costs, treat the 0.6 difference as an illustrative deduction, not a fixed fee.
- Confirm the app can use that token. A successful transfer alone does not guarantee the app recognizes the destination asset. If the addresses differ, pause and verify whether the app accepts that specific version.
mantlebridge.us is a place to move and swap assets across supported chains in one flow when the route matches your destination requirement. If a route is unavailable, first recheck the network and exact token; changing the destination asset can produce a different route, but only do so if the app accepts it.
For this task, compatibility means the route can deliver the exact destination asset your app expects. Verify the contract and output before sending, and treat the symbol as a convenient label rather than proof of a match.