Circle CCTP V2 is live on Sui

Circle said on October 8, 2026, that CCTP V2 is now live on Sui. The post puts the change in one line: sending USDC on Sui just got easier. Developers use Circle's burn-and-mint infrastructure, and the tools named on the card are an inbound fast transfer, programmable messaging, hooks, and more tooling for complex crosschain work. The post is here:

Sui had already posted the route the same morning. Native USDC can move between Sui and 29 other supported blockchains. Burned on the source chain, minted on Sui. Circle holds the mint authority, so the supply that arrives is the issuer's USDC, not a wrapped stand-in from a bridge. That is the sentence a payments app can use. The app does not have to design around a bridge to get dollars onto the chain.

A bridge, in the usual shape, locks a dollar on one chain and issues a different token on the next. The user then has to trust the lock, and the app has to know which version of the dollar it received. CCTP skips that receipt. The dollar leaves one chain by being burned, and the same issuer mints it on Sui. Sui's line for builders is to start payments and treasury products without designing around a bridge. The contract the app talks to is Circle's, and the unit the user holds at the end is USDC.

The steps are three, and Sui wrote them down. The app burns USDC on the source chain. The CCTP API attests the burn. Native USDC is minted on Sui. Sui then added the part that changes what a developer can do with the arrival. USDC that lands can be used in the transaction that receives it. Deposit, swap, or pay, in one transaction. The dollars and the action are not two trips.

Circle's card names the tools that make that trip programmable. Inbound Fast Transfer is the speed path onto Sui. Circle's CCTP documentation describes Fast Transfer as the option built for speed, with attestation in about 8 to 20 seconds. The Sui announcement specifies inbound, which is a burn somewhere else and a mint on Sui. Programmable messaging is the instruction that can ride with the dollars. Hooks, in the same docs, trigger an automated action on the destination chain after the asset arrives. A deposit can become a swap or a payment without a second transaction written by hand.

The distinction worth keeping is whose dollar it is. A bridge usually hands the user a receipt. CCTP destroys USDC on the chain it left and mints USDC on the chain it entered, and Circle is the only party that mints. Sui said that outright: the supply on Sui comes directly from the issuer. A firm that already holds USDC on another supported chain can move the same dollar, not a substitute, and spend it on arrival. Payments, a swap, and a treasury product are the three uses Sui named. The route is what makes each of them one transaction.

What comes next is the app that uses the hook. The route is live. The 29 chains are the ones Sui named. The mint is Circle's. A developer starts at the link on the post, developers.circle.com/cctp. Someone who used to bridge USDC onto Sui and then write a second transaction can now send the dollars and the instruction together. That is the line worth forwarding.