Review the USDC-to-Sui route only after confirming the source holds native Circle USDC rather than a bridged USDC variant.

Does the current native Sui Bridge panel list USDC?

No. The validator-secured Ethereum↔Sui selector currently lists ETH, WETH, USDT, WBTC, and LBTC. USDC was integrated through Circle CCTP as a separate burn-and-mint path and may appear through a dedicated route or compatible application rather than the native token list.

This distinction prevents users from searching for a nonexistent USDC allowance in the wrong bridge contract.

How does CCTP move USDC?

The source USDC contract burns the user’s amount through Circle’s Token Messenger. Circle’s attestation service confirms the burn message, and the destination contracts mint the same nominal amount of native USDC on Sui.

Unlike a liquidity bridge, CCTP does not depend on a pool of pre-funded bridged USDC. Unlike Sui Bridge lock-and-mint assets, it does not use Sui validator signatures for the cross-chain attestation.

Is Sui on CCTP V2?

Circle’s current supported chains and domains page lists Sui as domain 8 under CCTP V1 legacy support, not in the V2 supported-chain table. A route advertising CCTP V2 features for Sui should therefore be checked carefully against current Circle documentation.

The operational implication is that available transfer modes and attestation timing can differ from V2 chains such as Base or Arbitrum.

What is the canonical Sui USDC coin type?

Circle publishes the mainnet Sui USDC type as 0xdba34672e30cb065b1f93e3ab55318768fd6fef66c15942c9f7cb846e2f900e7::usdc::USDC on its USDC contract address page.

The received coin type should match this value when the goal is native Circle USDC.

Which source chains can feed a Sui USDC route?

Sui’s 2024 CCTP integration announcement named Ethereum, Arbitrum, Avalanche, Base, Noble, OP Mainnet, Polygon PoS, and Solana alongside Sui. Circle’s current V1 status should be checked because chain support and route frontends can evolve.

The source must hold native USDC supported by Circle, not a third-party wrapped version.

How is native USDC distinguished on the source?

Verify the issuer contract or mint, decimals, chain, and Circle support. On EVM chains, compare the token address with Circle’s official list. On Solana, compare the mint. A ticker such as USDC.e or a bridge-specific wrapper is not automatically eligible for CCTP burn.

Wrong source identity is the most important failure to eliminate before approval.

What fees does CCTP add?

Users pay source and destination gas according to the route implementation. Standard CCTP transfer does not require a currency conversion because USDC is burned and minted one-to-one in nominal units. An integrating application can still charge a service fee or add a relayer.

Read the actual transaction quote and identify who submits the destination receive message.

Does CCTP provide SUI for gas?

Native USDC can arrive in a wallet with no SUI. Whether a particular interface sponsors destination gas or includes a gas-drop service is route-specific. Do not assume the Sui Bridge validator subsidy for inbound native-bridge assets automatically applies to every CCTP integration.

Plan how the destination wallet will obtain enough SUI for its next transaction.

How should the transfer be verified?

Keep the source burn hash, Circle message or attestation identifier, destination receive transaction, Sui address, and USDC coin type. Confirm that the source supply decreased through a burn and that native Sui USDC was minted to the receiver.

This evidence differentiates CCTP from a pool-based bridge transfer.

When is the native Sui Bridge route the wrong choice?

It is the wrong panel when the required destination asset is Circle-native USDC. Choosing USDT or an Ether asset because USDC is absent does not preserve the intended token. Use a verified CCTP route or another route whose output is explicitly the canonical Sui USDC coin type.

USDC route assessed July 16, 2026. Circle currently classifies Sui under legacy CCTP V1 support.