# CCTP FAQ

<details>

<summary>What is CCTP?</summary>

Cross-Chain Transfer Protocol (CCTP) is a permissionless onchain utility that facilitates USDC transfers between blockchains via native burning and minting. With CCTP, USDC is effectively teleported from one blockchain to another.

</details>

<details>

<summary>How does CCTP differ from lock-and-mint bridging?</summary>

Lock-and-mint bridges are applications that lock a user’s native USDC within a smart contract on a source chain and then mint a synthetic or bridged form of USDC on a destination chain. This process incurs additional trust assumptions and can result in poor UX due to the fragmentation of liquidity.

In contrast, CCTP enables USDC to move securely 1:1 between blockchains via a native burn-and-mint process. The result is greater capital efficiency and unified liquidity with no creation of bridged forms of USDC. As a low-level primitive, CCTP can be embedded within existing bridge apps to replace their lock-and-mint functionality.

</details>

<details>

<summary>How does CCTP differ from liquidity pool bridging?</summary>

Liquidity pool bridges are applications that hold large pools of USDC on a source chain and a destination chain in order to facilitate cross-chain swaps for end users. This process incurs additional trust assumptions and fees associated with the liquidity tied up on each chain.

In contrast, CCTP enables USDC to move securely 1:1 between blockchains via a native burn-and-mint process. The result is greater capital efficiency and unified liquidity without the need for large pools of USDC tokens. As a low-level primitive, CCTP can be embedded within existing bridge apps to replace their liquidity pool functionality. Alternatively, CCTP could be used by the bridge provider to programmatically rebalance their liquidity pools behind the scenes and reduce operational costs.

</details>

<details>

<summary>Who is CCTP designed for?</summary>

CCTP is a permissionless protocol that you can integrate into your app, bridge, exchange, or wallet. It provides core infrastructure for cross-chain transfers. You can use CCTP to enable advanced cross-chain functionality at faster speeds and enhanced composability, or continue to use standard cross-chain functionality at standard speeds. For details, see the [CCTP overview](https://developers.circle.com/cctp).

</details>

<details>

<summary>Does CCTP require signing up with Circle?</summary>

No, CCTP is permissionless, which means any developer can integrate via [Circle’s docs](https://developers.circle.com/cctp) and [GitHub repository](https://github.com/circlefin).

</details>

<details>

<summary>What are the fees associated with cross-chain transfers via CCTP?</summary>

There is a gas fee charged on the source blockchain and on the destination blockchain. The app that integrates with CCTP is responsible for determining how gas fees are handled.

For fast transfers, an additional fee is collected when the stablecoin is minted on the destination chain. The fee is based on the amount minted. For more information, see the [CCTP fees](broken://pages/bac7c1a53b3bea89fbae2edfa8de2d0ac977aa43#fees) section.

</details>

<details>

<summary>What is the Fast Transfer Allowance in CCTP?</summary>

Circle’s Fast Transfer Allowance limits the total amount of USDC that can be minted using CCTP Fast Transfer before the corresponding burns on source chains reach finality. This mechanism caps the aggregate value of in-flight transfers awaiting hard finality, helping mitigate risk while enabling faster minting on destination chains. The allowance applies only to CCTP Fast Transfer and ensures that system-wide exposure to non-finalized burns remains within a defined threshold.

</details>

<details>

<summary>When will CCTP be available on additional chains?</summary>

CCTP is available on multiple blockchains, with more chains to be added over time. For the latest list, see [CCTP supported blockchains](/chainaiswap-docs/cross-chain-transfer-protocol/cctp-supported-chains-and-domains.md).

</details>

<details>

<summary>Can't I use Circle Mint to move USDC across chains? What about a centralized exchange?</summary>

Yes, Circle Mint is capable of moving USDC natively across chains. However, Circle Mint is a commercial product that is only available to qualified businesses approved by Circle.

Centralized exchanges typically hold various native forms of USDC liquidity on their platforms. Users with an account at a centralized exchange can deposit USDC (native to a given chain) into their exchange wallet, and then withdraw USDC (native to a different chain) to their external wallet.

In contrast, CCTP is permissionless. This means it’s accessible to any developer to seamlessly integrate into their apps and does not require onboarding to Circle. End users can move USDC through a CCTP-enabled app to any supported blockchain at any time. Developers can also compose new onchain experiences on top of CCTP within their apps.

</details>

<details>

<summary>How does a given quantity of USDC burned on the source chain become successfully minted on the destination chain?</summary>

When USDC is burned on the source chain, the event is automatically observed by Circle’s Attestation Service. The app facilitating the burn of USDC is responsible for fetching the signed attestation from Circle, which then enables CCTP to mint USDC on the destination chain.

</details>

<details>

<summary>Have the CCTP smart contracts undergone security audits?</summary>

Yes. The CCTP smart contracts have been independently audited by third-party security firms:

* CCTP was audited by [ChainSecurity (PDF)](https://6778953.fs1.hubspotusercontent-na1.net/hubfs/6778953/PDFs/ChainSecurity_Circle_CCTP_V2_audit%20\(1\).pdf) and [OtterSec (PDF)](https://6778953.fs1.hubspotusercontent-na1.net/hubfs/6778953/PDFs/public_evm_cctp_audit_final%20\(2\).pdf).
* CCTP (with Standard Transfer fee switch) was audited by [ChainSecurity (PDF)](https://6778953.fs1.hubspotusercontent-na1.net/hubfs/6778953/CCTP/ChainSecurity_Circle_CCTP_audit_2025-07.pdf).
* CCTP V1 (Legacy) was audited by [ChainSecurity (PDF)](https://6778953.fs1.hubspotusercontent-na1.net/hubfs/6778953/CCTP/ChainSecurity_Circle_Circle_EVM_Bridge_audit.pdf) and [Halborn (PDF)](https://6778953.fs1.hubspotusercontent-na1.net/hubfs/6778953/CCTP/Circle_Internet_Financial_EVM_Bridge_Smart_Contract_Security_Audit_Report_Halborn_Final.pdf).

Refer to the linked reports for detailed findings and audit results.

</details>

<details>

<summary>What happens if Circle's Attestation Service is unresponsive?</summary>

While its unavailability would temporarily preclude new burn messages from being signed, we anticipate robust uptime and availability similar to how our existing minting services operate today. You can always check [status.circle.com](https://status.circle.com/) for real-time updates on service availability.

</details>

<details>

<summary>How does CCTP affect existing bridged forms of USDC?</summary>

CCTP has no direct impact upon existing bridged forms of USDC.

</details>

<details>

<summary>How does CCTP affect Circle's plans to launch USDC on more blockchains?</summary>

Circle’s plans to bring USDC natively to more blockchain networks remain the same and will continue to grow. We envision CCTP establishing USDC as a universal liquidity layer for the Internet that is accessible to all.

</details>

For more information, see the [CCTP Technical Guide](broken://pages/bac7c1a53b3bea89fbae2edfa8de2d0ac977aa43).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://chainaiswap.gitbook.io/chainaiswap-docs/cross-chain-transfer-protocol/cctp-faq.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
