CCTP Fast vs Standard: Pick speed or savings

Circle’s Cross-Chain Transfer Protocol (CCTP) provides two attestation modes for native USDC burns: Fast and Standard. The difference is the finality threshold passed to depositForBurn. Fast uses confirmed finality with minFinalityThreshold at or below 1,000; Standard waits for finalized finality with the threshold at or above 2,000.

Circle’s documentation lists typical attestation times by mode and network. Fast attestation often completes in roughly 8–20 seconds on many routes. Standard attestation commonly requires minutes; on Ethereum and many OP-stack L2s the window is often 15–19 minutes. Some Standard routes run longer: Linea finality can take about 6–32 hours and Starknet often 2–4 hours.

Fast transfers incur a protocol fee charged by source chain and quoted in basis points. Circle’s September 2026 illustrative table shows Ethereum and Solana around 1 bps, Base and several L1-like networks near 1.3 bps, Arbitrum about 1.4 bps, some smaller networks 2–4 bps, and Starknet and Linea roughly 12–13 bps. On a $1,000 transfer those rates translate to cents or low-dollar amounts depending on route. Standard transfers are listed at 0 bps on the published chain list. By default the Fast fee is deducted when USDC is minted on the destination; an upfront-fee option exists so recipients can receive the full amount.

Developers set the mode by adjusting the finality threshold in depositForBurn or by setting a cctpMode flag. Circle exposes a live fee endpoint, GET /v2/burn/USDC/fees, for source and destination pairs. Circle’s guidance recommends fetching current rates and adding a 10–20% buffer when setting maxFee. MaxFee is the upper bound passed to depositForBurn; if the live Fast fee exceeds maxFee the burn can revert with no USDC burned, or the request can degrade to Standard if maxFee is below the Fast threshold. Circle’s resources also advise date-stamping fee quotes because rates can change.

Fast transfers consume a global Fast Transfer allowance managed by Circle; Standard transfers do not. Gas for the source burn and destination mint is paid in the chain’s native token and is separate from the USDC protocol fee. Some source chains do not offer a Fast mode because Standard attestation on those chains is already measured in seconds.

Operational notes in Circle’s documentation include confirming that the token burned is native Circle USDC rather than a bridged wrapper, monitoring Fast Transfer allowance relative to peak notional, and avoiding hardcoded fee tables. The documentation describes failure modes tied to maxFee and explains how Fast may degrade to Standard or revert if fee conditions are not met.

Use cases described in the documentation and technical guides note Fast for flows that require second-level settlement, and Standard for flows where zero protocol fee and hard finality are preferred. The protocol details and live fee API are available in Circle’s technical documentation and developer resources.