Connect, share wins, swap ideas, and chill with fellow community members

Member Lounge

Stablecoins are supposed to be simple. You hold it, you send it, the person on the other end receives it. That's the whole idea.

But here's the reality most people have to deal with. Ethereum has its own USDC. Base has its own USDC. Arbitrum, Solana, Avalanche, each one has USDC living on it. And they don't automatically talk to each other. So the moment a real person or a real business tries to move USDC from one chain to another, they run into a system that was never designed with them in mind.

Imagine telling a customer: yes, we accept USDC but only the Arbitrum version. If you have Base USDC you'll need to bridge it first, pick a route, wait somewhere between 30 seconds and 20 minutes depending on what you choose, and by the time it lands you'll receive slightly less than what you sent. We're not sure exactly how much less. It depends.

that's not exactly a business payment model design. Businesses don't sign up to hand customers a confusing flow and risk losing them before the payment even completes.

This is the problem CCTP was built to solve.

Most bridges are built on what's called a lock-and-mint model. You deposit your USDC on Chain A, the bridge locks it in a smart contract, and then mints a wrapped version of USDC on Chain B. You didn't really move USDC. You moved an IOU.

Some bridges mint wrapped assets. Others route through liquidity pools. Many combine both  which is where things get messy.

That wrapped token is only as good as the bridge backing it. If the bridge gets hacked and bridges get hacked your wrapped USDC is sitting on a chain backed by nothing. In February 2022, Wormhole's bridge was exploited for $326 million in a single transaction. The attacker found a deprecated security function, forged a signature, and minted 120,000 ETH from thin air. The attacker forged a signature and minted unbacked ETH out of thin air breaking the system's backing entirely, everything built on top of it was suddenly at risk. The Ronin bridge went down the same year for $620 million, attributed to the North Korean Lazarus Group. These weren't edge cases. In total, over $2 billion has been lost to bridging hacks. The attack surface for liquidity-pool bridges is enormous because the pools themselves are exactly what attackers go after.

Then there's the slippage problem. Because When bridges rely on liquidity pools to route transfers, slippage becomes part of the experience, the size of your transfer affects the rate you get. Move a large amount and the pool rebalances around you. You pay for that rebalancing. On Solana alone, there were 11 distinct verified wrapped USDC variants, and numerous unverified ones LI.FI every bridge with a Solana route created its own version, fragmenting liquidity across a dozen representations of the same dollar. None of them behave identically. Some DeFi protocols only accept certain versions. You'd land funds on a chain and then discover you needed another swap just to use them where you intended.

This is the environment CCTP was built to replace.

What CCTP actually does "The burn-and-mint model"

CCTP works differently at its foundation. There are no pools so there is nothing to drain.

When you move USDC from Base to Arbitrum through CCTP, the USDC on Base is burned from supply entirely. Circle's attestation service observes that burn and generates a cryptographic proof confirming it happened. That proof gets submitted to Arbitrum, where a smart contract verifies it and mints the exact same amount of native USDC directly to your wallet. 100 USDC in. 100 USDC out. Not a wrapped or a synthetic version. The same native USDC that Arbitrum's entire ecosystem recognizes.

No slippage because there's no pool rebalancing around your transfer or counterparty risk because nothing is locked anywhere. Since launching in April 2023, CCTP has processed over $37 billion in transfers. That number reflects institutions and protocols choosing it specifically because the output is predictable at any size and because the trust model is simple. Circle signs off on every transfer. That's it.

CCTP V1 had one limitation worth knowing: it waited for the source chain to fully finalize before minting on the other side. From Ethereum and its L2s, that finality window runs 13 to 19 minutes. Acceptable for treasury management and rebalancing but it isn't acceptable if you're building a payment product where someone is standing in front of a checkout screen.

CCTP V2, launched in March 2025, addresses this with two new features. Fast Transfer lets the attestation happen before full finality, settling the transfer in seconds instead of minutes practically instant from the user's perspective. Standard Transfer (V1 behavior) still exists for flows that don't need speed and want near-zero fees. You choose based on what you're building.

The second feature is Hooks. Before Hooks, cross-chain actions were sequential: transfer lands, then you trigger whatever needs to happen next. Hooks let developers attach post-transfer logic to the transfer itself, so the USDC arrives and the next action (a deposit, a swap, an update) executes in the same transaction. Less coordination overhead and fewer failure points.

Today, CCTP V2 runs on Arbitrum, Avalanche, Base, Codex, EDGE Chain, Ethereum, HyperEVM, Ink, Linea, Monad, Morph, OP Mainnet, Plume, Polygon PoS, Sei, Solana, Sonic, Starknet, Unichain, World Chain, and XDC as well with more chains being added. The platforms already built on it include Stargate, Interport, LI.FI, Mayan, Socket, and Wormhole. When you use any bridge aggregator to move USDC and see "CCTP" as a route option, that's this infrastructure underneath.

CCTP itself charges no protocol fee. What you pay is chain gas, which on L2s is fractions of a cent. Circle also launched USDC Bridge, a consumer-facing product built on the same burn-and-mint mechanic, with clear upfront fees and automatic destination gas handling. That convenience comes at a cost though: around 0.24 USDC on a 100 USDC transfer versus under a penny routing through CCTP directly on an aggregator. Same infrastructure underneath but the fee is more when I tried USDC bridge. Its definitely worth knowing before you decide how to build.

CCTP solves the transfer problem well. But there is a step beyond transfer that takes the whole idea further.

Circle's Gateway gives wallets and apps a unified USDC balance, one balance that is instantly accessible across all supported chains in under 500 milliseconds. You deposit USDC once, and from that point you can spend or move it on Ethereum, Base, Arbitrum, Solana, or any of the supported chains without initiating a new bridge transaction each time. The chain becomes an invisible implementation detail rather than something the user has to think about.

For a normal user that means: you have USDC, and you can pay anywhere USDC is accepted, regardless of which chain the merchant or app sits on. For a business it means serving users across chains without holding separate capital reserves on each one, no pre-positioning or rebalancing, its just one integration.

CCTP made the transfer reliable but Gateway makes the transfer disappear entirely from the user experience. That's where this is heading.

Why this matters if you're building on Arc

When you integrate CCTP into what you're building, you're not routing users through a pool that can be drained. You're not giving them wrapped tokens that behave differently across protocols. You're not making them wait 15 minutes for a cross-chain payment to settle.

Gateway on Arc goes further,  a unified USDC balance that works across chains simultaneously, no bridging required at all. But CCTP is the foundation that makes all of it possible. The burn-and-mint model is the reason multi-chain USDC maintains its integrity. The reason a dollar sent on Base arrives as the same dollar on Arbitrum.

The tooling is real. The volume is real. The integrations are real. Builders who understand what CCTP actually does will make better product decisions than builders who just accept bridging complexity as inevitable.

https://x.com/atomic_kurogane/status/2048646156067144062

Builder Field Notes Series 3: STABLECOINS SHOULD BE SIMPLE

Home

Forum

Events

Content

Courses

People

Contributors

Albums

Groups

Chat

Channels

Not being used

Help

Join the global network of builders developing the Economic OS for the internet. We’re reimagining how value moves, creating the tools that make the economy work for everyone.

Arc House

Profession

Join a global network of builders developing the Economic OS for the internet. We’re reimagining how value moves, creating the tools that make that economy work for everyone. 

Arc House | Build the economic OS for the internet with us

Copyright

Terms of Service

Privacy

Code of Conduct

Your Privacy Choices

It looks like there is no account associated with the email you provided. The event is for members only. Please complete the application to join our community first.

Thank you for your interest in joining us

Thanks for your interest in joining the event. However, your account is still pending. Once it's approved, you'll be able to register for the event. Please contact us via noreply@arc.network if you need support.

Pending Approval

Login to the The Arc Community Hub community to connect with others, attend community events, and more!

Login or Sign Up for even more

To unlock all parts of the community complete your profile using verifiable and real information.

Hey, complete your profile

It looks like there is no account associated with the email you provided. Please complete the application to join our community.

Thank you for your interest in joining Arc House.

Thanks for your interest in joining Arc House. We will review your request shortly and email you once it's approved. Meanwhile, please feel free to contact us via noreply@arc.network for any questions.

Accounts are unapproved when profile information cannot be verified or when activity patterns indicate spam, inorganic participation, or behavior that undermines trust in the program.

To strengthen your profile for future consideration, sign in with a verified LinkedIn account, use real and current profile information, and participate constructively in other community spaces.

Commercial customers should raise concerns through their support channel.

https://www.arc.network/community-guidelines