Skip to main content
SaucerSwap lists tokens. It does not issue, back, or vouch for them. A bridged token is only as good as its bridge and its issuer, and the same symbol can be a different token, so check the token ID. You can lose some or all of what you put in. This page is information, not advice.

​
Which version do I have?

Native tokens. USDC is Circle’s fiat-backed stablecoin, issued natively on Hedera as an HTS token. Check the token ID on Circle’s USDC page. Axelar tokens (names ending in .axl). These came to Hedera through Axelar. SaucerSwap’s bridge routes over Axelar and LayerZero, and issuers can deploy an existing Hedera token to other chains with Axelar’s Interchain Token Service. What backs each .axl token is set by its issuer: read Axelar’s page and the token’s own issuer. LayerZero tokens (USDT0, WETH, WBTC). SaucerSwap lists pools for these and routes the bridge over LayerZero. What backs each one is set by its issuer: read the issuer’s own page first. Bridges can pause. On 1 May 2026 SaucerSwap posted that WBTC bridging had resumed after BitGo restored its verification step. Old [hts] tokens (USDC[hts], WBTC[hts], WETH[hts], USDT[hts]). These came through Hashport, which shut down on 31 May 2026. They cannot be redeemed for the original asset. Do not treat them as the real thing. See the FAQ. Do not assume two tokens with one symbol are interchangeable. For example, the WETH/HBAR order-book market uses direct ERC-20 WETH, not an HTS-wrapped one (markets).

​
What can go wrong

SaucerSwap’s terms name these risks: token-issuer risk, stablecoin reserve and redemption risk, freeze or blacklist functions, bridge risk, admin-key and upgrade risk. In plain words:
  • The bridge or its message layer fails or pauses.
  • The issuer freezes the token or cannot redeem it.
  • An admin key or an upgrade changes how the token behaves.
  • You hold a look-alike with the same symbol.
  • A transfer looks stuck, or the token does not show up. Most stuck transfers are still in flight. Look up the transaction hash on AxelarScan. On Hedera, associate the token with your account. See bridge troubleshooting.
The terms also say a token being available in the app is not a review, a reserve check, or a promise that it is backed or redeemable (section 12).

​
Check it yourself

  • Look up the token on HashScan. Compare its token ID with the issuer’s page.
  • Read the issuer’s own page for what backs it and how to redeem.
  • Track a bridge transfer on AxelarScan by transaction hash or wallet address.

​
Next steps

Bridge routes explained

The Axelar and LayerZero routes, and the Hashport decommission notice.

Bridge tutorial

Use the in-app bridge step by step, with troubleshooting.