USDC or USDT on Mantle? Choose by where you’ll use it
USDC and USDT0 both work on Mantle, but token versions, app support and bridge routes decide which is easier to use, pay fees for and move back out.
BitCurrent Newsroom2 min read
Choose USDC if the app you plan to use requires USDC; choose USDT0 if it requires Mantle’s current Tether-linked USDT. Both are dollar stablecoins, but bridging them can leave you with different token versions and different routes back to other networks.
Which versions of USDC and USDT are on Mantle?
Mantle’s token list pairs USDC with a Mantle version of the Ethereum token, and lists both USDT0 and legacy USDT (BRIDGED). The tickers can look familiar, but the contract and route matter: a receiving app may accept one version and reject another.
USDT0 uses an omnichain route, while the legacy USDT entry uses Mantle’s standard bridge mapping. USDC also has a mapped Mantle version. For the mechanics behind moving assets, the fuller mantle bridge guide explains what happens across networks.
What does the bridge move, and what does it cost?
A bridge transfers a token between networks; it does not automatically swap USDC for USDT or make every version interchangeable. The route you select determines which token arrives, so check the destination asset before signing.
Fees depend on the route and network activity. Ethereum transactions require ETH for gas, including a token approval when needed; transactions on Mantle require MNT. Compare the amount you expect to receive and the fees shown before confirming, especially if you need to withdraw back to Ethereum.
How should I choose before sending?
Check the destination app first. If it names USDC, use the USDC route; if it asks for USDT0, use that route rather than assuming legacy bridged USDT will work.
Confirmed: Mantle lists all three token entries, and the token versions use different bridge mappings. Still open for your particular transfer: whether your wallet, destination app and return route support the exact version you receive, and what the live fees will be.
For most users, app compatibility is the deciding factor. Use the token the destination supports, then verify the network, token name and receiving address before sending.