Дослідження з перевіркою джерел: Circle CCTP V2 FAST

Decision Matrix

Source Map

• Circle Help Center: Getting started with CCTP (circle-cctp-help)
• Circle: CCTP Cross-Chain Transfer Protocol (circle-cctp-product)
• Circle: CCTP V2: The future of cross-chain (circle-cctp-blog)
• Circle: Cross-Chain Transfer Protocol V2 White Paper (circle-cctp-whitepaper)

Control Notes

1. Transfer mode

Transfer mode is the point where public documentation must become an operating rule. In this package, it means fast and standard transfers imply different timing and finality assumptions. The practical action is to choose mode deliberately and document the reason. The unresolved edge is whether a route temporarily lacks fast capacity, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

2. Fee ceiling

Fee ceiling is the point where public documentation must become an operating rule. In this package, it means maxFee and feeExecuted make the cost boundary explicit. The practical action is to set a maximum fee and record actual fee after attestation. The unresolved edge is whether fee changes occur before execution, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

3. Attestation state

Attestation state is the point where public documentation must become an operating rule. In this package, it means the destination action depends on Iris attestation. The practical action is to query attestation status before retrying. The unresolved edge is whether source-chain reorg risk remains, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

4. Hook payload

Hook payload is the point where public documentation must become an operating rule. In this package, it means hooks can automate destination actions but add behavior to review. The practical action is to treat hookData as part of the transaction intent. The unresolved edge is whether downstream action fails after mint, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

5. Expiration

Expiration is the point where public documentation must become an operating rule. In this package, it means fast messages can include expiration behavior. The practical action is to track expirationBlock and define a retry rule. The unresolved edge is whether delayed execution creates duplicate handling, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

6. Fallback path

Fallback path is the point where public documentation must become an operating rule. In this package, it means a failed fast route may require standard transfer or manual recovery. The practical action is to define fallback before burning funds. The unresolved edge is what support evidence is needed for a stuck transfer, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

Known Unknowns

• whether a route temporarily lacks fast capacity
• whether fee changes occur before execution
• whether source-chain reorg risk remains
• whether downstream action fails after mint
• whether delayed execution creates duplicate handling
• what support evidence is needed for a stuck transfer

Practical Takeaway

Circle CCTP V2 changes the cross-chain USDC decision from bridge selection to finality and attestation controls. Circle describes CCTP as a permissionless utility that transfers native USDC by burning on the source chain and minting on the destination chain. Circle's CCTP V2 material says Fast Transfer can provide faster-than-finality settlement, while Standard Transfer follows blockchain finality. The white paper defines fields such as maxFee, feeExecuted, expirationBlock, hookData and finalityThresholdExecuted. A safe transfer map records source chain, destination chain, finality mode, fee ceiling, attestation status, hook payload, expiration, mint recipient and fallback path. The article stops at the evidence boundary. It helps the reader decide what to inspect next without converting public documentation into a promise that a private account, wallet, API key, pool route, stablecoin balance, tokenized asset or policy framework will work under every future condition.