Circle Cross-Chain Transfer Protocol (CCTP)

A dated reading of what is claimed, reported, and independently verified in the current evidence.

Current reading

Readiness band and full integer triple

AI-assisted assembly · derived results

Readiness band

Watch

Primary summary from verified readiness

Evidence strength Strong

Decision

Agent-assisted assessment · independently reviewed · 2026-10-05

Use current CCTP for supported USDC routes if Circle's trust model and route-specific controls fit your application.

Why: Production integrations support practical use, while limited audit coverage, attestation disruptions and integration failures require operational safeguards.
Next: Verify deployed contracts and actual token receipt, test delayed finalization, and migrate or remove legacy routes before their applicable shutdown dates.

Constraints

Circle attestation availability and privileged administration remain trust dependencies.
Integrations must verify trusted message endpoints and actual minted balances.
Audit coverage must match deployed code, configuration and destination chains.
Applications need handling for delayed attestations and incomplete finalization.
Legacy routes require migration or removal; Noble has no V2 replacement.
Onchain fees and transfer-mode behavior require application-specific handling.

Evidence summary

AI-assisted assembly

Counts and dates only. Raw signals, private excerpts, trust records, and internal corpus material are not published here.

Publication record

Revision 4