# Circle CCTP: moving native USDC by burning and minting

Circle’s Cross-Chain Transfer Protocol, or CCTP, can move native USDC between supported chains by burning on the source chain and authorizing minting on the destination through Circle’s attestation infrastructure. It avoids a conventional locked-USDC wrapper for that route, but still depends on supported contracts, chain settlement and the attestation process.

Evidence: [CCTP overview](https://developers.circle.com/cctp); [Cross-Chain Transfer Protocol](https://www.circle.com/cross-chain-transfer-protocol)

Canonical: https://degreesofsatoshi.com/encyclopedia/circle-cctp/
Published: 2026-10-02
Substantively modified: 2026-10-02
Independently verified by an automated reviewer: 2026-10-02T18:15:23.891Z
Data current through: 2026-10-02

AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied.

## Key facts

- **USDC route:** Native USDC transfers use a burn-and-mint mechanism. ([CCTP overview](https://developers.circle.com/cctp))
- **Attestation:** The destination operation relies on a signed attestation from Circle’s infrastructure. ([Cross-Chain Transfer Protocol](https://www.circle.com/cross-chain-transfer-protocol))
- **Scope:** Supported assets, chains and transfer modes are version-specific. ([CCTP overview](https://developers.circle.com/cctp))

## Follow the transfer across both chains

For a native USDC route, the source-chain operation first burns the specified USDC amount. An attestation is then obtained, and a destination-chain transaction uses it to complete the minting process.

A successful source burn is not the same as a completed destination mint. Track the source transaction, message or attestation state and destination receipt separately.

Evidence: [Cross-Chain Transfer Protocol](https://www.circle.com/cross-chain-transfer-protocol)

## Native issuance changes one dependency, not all of them

For native USDC, the destination token is issued through the supported Circle mechanism rather than merely representing a claim on USDC locked in a generic bridge.

Issuer controls and redemption terms still apply. The transfer also retains cross-chain operational dependencies, including the attestation service and destination execution.

Evidence: [CCTP overview](https://developers.circle.com/cctp); [USDC Terms](https://www.circle.com/legal/usdc-terms)

## Do not assume all CCTP routes have identical semantics

Documentation retrieved October 2, 2026 describes different transfer modes and expanded non-USDC asset support. Some third-party routes use wrapping, so the native-USDC explanation must not be extended to every supported asset.

Check the exact version, source and destination domains, fees and finality requirements for a route. This article does not promise a fixed completion time.

Evidence: [CCTP overview](https://developers.circle.com/cctp)

## Questions

### Does a CCTP burn mean the recipient already has tokens on the other chain?

No. The attestation and destination execution still need to complete. A source-chain receipt establishes only the source stage of the transfer.

Evidence: [Cross-Chain Transfer Protocol](https://www.circle.com/cross-chain-transfer-protocol)

## Claims and scope

### circle-cctp-quick-answer

Circle’s Cross-Chain Transfer Protocol, or CCTP, can move native USDC between supported chains by burning on the source chain and authorizing minting on the destination through Circle’s attestation infrastructure. It avoids a conventional locked-USDC wrapper for that route, but still depends on supported contracts, chain settlement and the attestation process.

Scope: {"collection":"stablecoins","dataAsOf":"2026-10-02","blockHeight":null}

### circle-cctp-fact-usdc-route

USDC route: Native USDC transfers use a burn-and-mint mechanism.

Scope: {"collection":"stablecoins","dataAsOf":"2026-10-02","blockHeight":null}

### circle-cctp-fact-attestation

Attestation: The destination operation relies on a signed attestation from Circle’s infrastructure.

Scope: {"collection":"stablecoins","dataAsOf":"2026-10-02","blockHeight":null}

### circle-cctp-fact-scope

Scope: Supported assets, chains and transfer modes are version-specific.

Scope: {"collection":"stablecoins","dataAsOf":"2026-10-02","blockHeight":null}

## Sources

- [CCTP overview](https://developers.circle.com/cctp) — Circle. Native USDC transfer uses source-chain burning, Circle attestation and destination minting. Locator: How CCTP works; Burn and mint. Retrieved: 2026-10-02T17:03:43.290Z.
- [Cross-Chain Transfer Protocol](https://www.circle.com/cross-chain-transfer-protocol) — Circle. Issuer-described attestation dependency in cross-chain asset transfers. Locator: Burn; Attestation; Mint. Retrieved: 2026-10-02T17:33:31.537Z.
- [USDC Terms](https://www.circle.com/legal/usdc-terms) — Circle. Non-EEA USDC holder terms, eligibility, redemption and restrictions; not an unconditional promise to every holder. Locator: Sections 1–4, 8, 13, 15–17. Retrieved: 2026-10-02T17:03:43.080Z.

## Revision history

- 2026-10-02: First publication after primary-source research and independent automated verification.

## Cite this entry

Degrees of Satoshi editorial project. “Circle CCTP: moving native USDC by burning and minting.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/circle-cctp/