Table of Contents
Circle's Cross-Chain Transfer Protocol burns native USDC on the source chain and mints native USDC on the destination, so the balance you hold at the end is still Circle-issued USDC, not a wrapped bridge claim.
That is not a lock-and-mint. A conventional bridge locks your tokens and issues a different instrument.
CCTP is a burn-and-mint. It is not a lock-and-mint wrapper.
Key Takeaways
- CCTP burns native USDC on the source chain and mints native USDC on the destination.
- You still hold Circle-issued USDC when the transfer completes.
- A lock-and-mint bridge creates a wrapper Circle does not redeem.
- Fast Transfer attests after confirmation; Standard Transfer waits for hard finality.
- Circle charges a protocol fee on Fast Transfer only.
- The destination still needs a gas token before you can send the USDC onward.
CCTP Is Burn-and-Mint, Not a Bridge Wrapper
Circle describes CCTP as a permissionless onchain utility. It moves USDC 1:1 by destroying it on one blockchain and creating the same amount on another.
Circle's CCTP page contrasts that with lock-and-mint bridges, which lock native USDC in a smart contract and mint a wrapped form on the destination. Liquidity-pool bridges instead pre-fund USDC on both sides and swap you out of a pool.
The token that arrives through CCTP is native USDC on the destination chain. That is a different fact from how to tell native USDC from bridged USDC, which is the identification test after the transfer lands.
Three Steps: Burn, Attest, Mint
Circle's transfer is three steps. Apps, wallets, and Circle's USDC Bridge all run the same sequence.
First, USDC is burned on the source chain. A depositor calls TokenMessenger, the minter burns the tokens, and a message is emitted.
Second, Circle's attestation service (Iris) observes the burn and signs the message after the required finality. The app then fetches that signed attestation.
Third, the signed message is submitted on the destination chain. MessageTransmitter validates it and native USDC is minted to the recipient.
You do not need a Circle Mint account to use CCTP. Circle states the protocol is permissionless infrastructure that any developer can integrate, and the USDC Bridge is Circle's own consumer frontend on top of it.
Canonical CCTP is V2. Circle's V1 (Legacy) phase-out commenced on 31 July 2026.
Fast Transfer Versus Standard Transfer
The wait is an attestation wait, not a liquidity wait. Circle will not sign until the source burn reaches the finality level you requested.
Circle's finality page splits the two modes. Fast Transfer attests after the burn is confirmed and included in a block, typically in seconds, and is capped by a global Fast Transfer allowance.
Circle's published Fast Transfer averages are about 8–20 seconds depending on the source chain. Standard Transfer attests after hard finality, when a chain reorganization is unlikely.
Circle's published averages for Ethereum and several L2s are about 15–19 minutes. Some source chains attest in seconds; some L2s take hours.
Fast Transfer is not offered as a source on every CCTP chain. Circle disables it where standard attestation is already fast.
Do not treat a mempool sighting as arrival. Arrival is a successful mint of native USDC on the destination.
What You Pay
Circle's CCTP fees page states that CCTP charges protocol fees on Fast Transfers only, and that Standard Transfers are free. Fast Transfer fees vary by source blockchain in a published range of 0–13 basis points, and Circle says those rates can change.
By default the Fast Transfer fee is deducted when USDC is minted on the destination. Circle also documents an upfront-fee path so the recipient can receive the full amount.
Gas is separate from the protocol fee. You pay the source chain to burn, and someone pays the destination chain to mint.
The USDC that arrives still cannot move without the destination network's native token, which is the same constraint as why you need a second token to send stablecoins. Fund a small gas balance on the destination before you need the USDC to leave that wallet.
CCTP Versus a Conventional Bridge
Treat the rail as the instrument test. The table is the working distinction.
| Check | CCTP burn-and-mint | Lock-and-mint bridge | Liquidity-pool bridge |
|---|---|---|---|
| Mechanism | Burn on source, mint on destination | Lock on source, mint a wrapper | Swap out of pre-funded pools |
| Token you receive | Native Circle-issued USDC | A bridged or wrapped claim | Native USDC only if the pool pays that contract |
| Who issues the destination token | Circle | The bridge operator | Circle, if the payout is native |
| Redeemable at Circle | Yes, for eligible holders of native USDC | No; Circle does not redeem the wrapper | Yes, only if you received native USDC |
| Extra trust | Circle's attestation of the burn | The lock contract and the wrapper | Pool solvency and the bridge operator |
A CCTP mint does not create USDC.e. If a UI still delivers a wrapped ticker, you used a different rail.
Confirm the destination contract against Circle's published address using how to check the official USDC or USDT contract. A logo match is not the test.
Before You Send
Name both chains in writing. "Bridge my USDC" is not an instruction.
Confirm the source token is native USDC on a chain Circle currently lists for CCTP. CCTP burns the Circle-issued contract; a wrapper cannot be burned as USDC.
Confirm the destination is also a current CCTP domain. Circle publishes that list on its supported-blockchains page, and the list is not the same as every chain that shows a USDC ticker.
After the mint, match the destination token page to Circle's address. Then treat the credit as native USDC under existing receive controls.
Issuer redemption did not change because you changed chains. How to redeem a stablecoin for dollars still starts from eligible native USDC and a Circle Mint account.
This Is Not Chain Deprecation
CCTP moves native USDC between chains Circle still supports. It is not a rescue rail after an issuer leaves a network.
What happens when a stablecoin issuer drops a blockchain is a different failure. Minting and redemption end, and a transferable balance is no longer a dollar claim.
If Circle is still issuing native USDC on both sides, CCTP is the transfer. If it is not, stop and treat the token as an unsupported instrument.
Conclusion
How do you transfer USDC between chains without a bridge? Use CCTP: burn native USDC on the source chain, wait for Circle's attestation, and mint native USDC on the destination.
The asset at the end is still Circle-issued USDC. A lock-and-mint wrapper is a different token.
FAQs
1. How do you transfer USDC between chains without a bridge?
Use Circle's Cross-Chain Transfer Protocol, which burns native USDC on the source chain and mints native USDC on the destination. Wallets, apps, and Circle's USDC Bridge all run that burn-attest-mint sequence.
2. Is CCTP the same as a lock-and-mint bridge?
No: Circle states that lock-and-mint bridges lock native USDC and mint a wrapped form, while CCTP destroys source USDC and issues native USDC on the destination. You do not receive a bridged wrapper.
3. Do I still hold Circle-issued USDC after a CCTP transfer?
Yes, if the mint completed against Circle's native contract on the destination chain. Confirm that contract against Circle's published address before you book the credit.
4. How long does a CCTP transfer take?
Circle attests Fast Transfers after confirmation, typically in about 8–20 seconds on supported source chains, and Standard Transfers after hard finality. Published Ethereum and L2 Standard times are often about 15–19 minutes, and some L2s take hours.
5. What does a CCTP transfer cost?
Circle charges a protocol fee on Fast Transfer only; Standard Transfer has no CCTP protocol fee. You also pay network gas on the source burn and on the destination mint, and Fast Transfer fees vary by source chain.
This content is provided for informational and educational purposes only and does not constitute financial, investment, legal, or tax advice; no material herein should be interpreted as a recommendation, endorsement, or solicitation to buy, sell, or hold any financial instrument, and readers should conduct their own independent research or consult a qualified professional.
){kind=link}