Circle’s Cross-Chain Transfer Protocol (CCTP) went live on Sui on October 8, 2026. Native USDC can now be burned on another supported network and minted on Sui, or burned on Sui and minted elsewhere, without a wrapped token in between. Circle added Sui mainnet and testnet as CCTP domain 8 in its release notes that day, and the Sui network announced that USDC “can now move between Sui and 29 other supported blockchains.”
The timing matters for developers. Until this release, Sui was one of two networks that Circle’s documentation still listed as served only by the original version of the protocol, now called CCTP V1 (Legacy), and that version is being switched off.
How a CCTP transfer to Sui works
CCTP moves USDC by burn and mint. An application burns USDC on the source chain, Circle’s attestation service confirms the burn, and the same amount of native USDC is minted on the destination chain. Because Circle’s own contracts do the minting, the USDC that arrives on Sui is Circle-issued USDC, not a bridge’s IOU. Our explainer on native and bridged stablecoins covers why that difference matters to a holder.
On Sui, Circle’s package reference says CCTP is implemented in four Move packages (MessageTransmitterV2, TokenMessengerMinterV2, StablecoinHandler and CctpExtensions) and uses Sui’s programmable transaction blocks to compose the required calls in a single transaction.
What Sui supports and what it does not
Circle’s supported blockchains table lists these capabilities for Sui as of October 15, 2026:
| Capability | Sui |
|---|---|
| Standard Transfer as a source | Yes |
| Fast Transfer as a source | Not applicable |
| Fees paid upfront on the source chain | No |
| Destination for the Forwarding Service | No |
| Destination for transfers | Yes |
Circle marks Fast Transfer “N/A” on chains where standard attestation is already fast enough that the faster option adds little.
The V1 deadline behind the launch
Circle’s migration guide says deprecation of CCTP V1 (Legacy) begins on October 31, 2026 and completes on December 1, 2026. The guide had named Noble and Sui as the V1 chains without V2 contracts and said Sui would be supported by V2 before the deprecation starts. The October 8 release delivers that. Noble remains listed as V1-only.
Circle says users will not lose access to funds during the phase-out: pending V1 redemptions remain available, and message limits tighten over time until no new V1 burns can be started. Integrations still on V1 must move to new contract addresses, new function signatures and new /v2/ API endpoints.
What it means for USDC holders on Sui
For someone holding USDC on Sui, nothing changes about the token itself. What changes is the route in and out: wallets and apps that adopt the new contracts can move USDC between Sui and other CCTP networks as native USDC on both ends. Before moving funds, check that the app names CCTP as the route and that the destination address belongs to the right network. Our network selection guide explains why the same ticker on two chains is not interchangeable, and the USDC entry in our stablecoin list covers its issuer and redemption terms.
