USDC on Sui: asset identity, decimals, and transfer paths

USDC on Sui is identified by its network and full coin type, not by the ticker alone. Circle's USDC on Sui page describes the Sui deployment as native USDC and warns that bridged forms such as wUSDC are not issued by Circle. That distinction affects deposits, routes, redemptions, and whether an application recognizes the asset.

Native type versus a same-named token

Circle's support documentation lists native Sui USDC as:

0xdba34672e30cb065b1f93e3ab55318768fd6fef66c15942c9f7cb846e2f900e7::usdc::USDC

The same page identifies a Wormhole bridged form as a different coin type. A wallet can display “USDC” for both, but the type identifier is part of the asset identity. Verify the full type in the wallet, the destination service, and the application's supported-asset documentation. Do not send a bridged token to a destination that accepts native USDC merely because both labels look familiar.

This is an issuer and integration check, not a claim that every bridge is unusable. Circle's migration guidance explains the difference between the native Circle-issued deployment and the earlier bridged form. The right asset depends on the destination's documented support and settlement path.

Six decimals and atomic units

Sui transactions carry integer quantities. Circle's developer article states that USDC uses six decimal places, so one human USDC equals 1,000,000 atomic units. A simple example is:

1.25 USDC × 1,000,000 = 1,250,000 atomic units

The reverse is 1,250,000 ÷ 1,000,000 = 1.25 USDC. Sui's transaction-payment documentation uses 5_000_000n as a 5 USDC example, which provides the same unit conversion in code. Keep the raw integer and the formatted amount together when checking a transfer; a decimal mistake can turn a valid-looking request into the wrong amount.

Three checks before a transfer

For a wallet transfer, verify the Sui network, native type, recipient, six-decimal amount, and SUI gas details. The Sui object model explains why a coin is represented through typed onchain objects with ownership and identity. Save the digest after signing and check the recipient's resulting state.

For a DEX route, verify that the route supports the exact native coin type. A quote for another USDC variant is not a quote for native Sui USDC. Check output, minimum received, slippage, and network gas separately from any application fee.

For a provider or exchange deposit, use its current native-USDC instructions and destination network. Circle explicitly warns that unsupported bridged assets sent to Circle Mint may not be recoverable. A provider's “sent” status is not proof that the destination credited the balance.

Questions that settle the ambiguity

• Does the destination name the native Sui type, or only the ticker?
• Is the amount shown in human units while the transaction carries atomic units?
• Does the route or provider support native USDC on Sui mainnet?
• Which digest, receipt, or provider record will prove completion?

Use how to fund a Sui wallet for the network handoff and how a SUI-to-USDC route works for quote and settlement checks. The asset identity comes first in both paths.