CCTP Enables Native USDC Across Chains
Diving deeper into
Circle
This eliminates the need for risky third-party bridges and ensures USDC remains native across all supported blockchains rather than existing as wrapped versions.
Analyzed 7 sources
Reviewing context
CCTP turns cross chain transfer from a liquidity and custody problem into a token lifecycle event. Instead of parking USDC in one bridge contract and issuing a synthetic copy somewhere else, Circle destroys the original token on chain A and recreates the same amount on chain B after attesting to the burn. That keeps USDC redeemable, fungible, and recognizable as native USDC everywhere Circle supports it.
-
Wrapped bridge systems usually work by locking an asset on one chain and minting a claim token on another. That creates extra trust in the bridge contract and often fragments liquidity into versions like USDC.e, where apps, exchanges, and users have to track which version they actually hold.
-
CCTP uses burn and mint instead. Circle launched it in 2023 to let apps move native USDC across chains, and by late 2025 it had expanded to 17 supported blockchains and more than $126B in cumulative volume. That scale matters because the more routes use the same native asset, the less routing friction developers need to hide from users.
-
This also shifts Circle from being just an issuer to being a coordination layer for multichain dollars. Even competing bridge and messaging products like Wormhole and LayerZero integrations increasingly use CCTP when the goal is to land as native USDC rather than a wrapped representation.
The next step is a multichain payments stack where chain choice becomes a back end detail. As Circle adds forwarding, bridge tooling, and more native USDC routes, the winning networks and apps will be the ones that let users move dollars across chains without ever touching a wrapped asset or thinking about bridge risk.