Recherche vérifiée par sources: Circle CCTP V2 Attestation

Decision Matrix

Source Map

• Circle Docs: Cross-Chain Transfer Protocol (circle-cctp)
• Circle Docs: CCTP Technical Guide (circle-attestation)
• Circle Docs: Supported Chains and Currencies (circle-supported-chains)

Control Notes

1. Source chain

Source chain is the part of the decision where a public source has to become an operating rule. In this package, it means the burn or send event begins on a specific network. The useful action is to record chain, transaction and message hash. The unresolved edge is chain reorg or finality assumptions, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.

For an operator, source chain should be recorded before funds, account access, wallet recovery, API order flow, document exports, tax records, whitelist changes, chain transfers, event-contract trades or tokenized-asset decisions become material. The record can stay simple: the official source URL, the date checked, the product or network under review, and a non-secret note describing why the next step is acceptable. Screenshots should avoid balances, identity documents, tax identifiers, API keys, recovery phrases, private keys, passphrases, verification codes and support-ticket private data.

2. Destination chain

Destination chain is the part of the decision where a public source has to become an operating rule. In this package, it means the destination route must be supported for the intended asset. The useful action is to check current supported-chain documentation. The unresolved edge is new chain rollout timing, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.

For an operator, destination chain should be recorded before funds, account access, wallet recovery, API order flow, document exports, tax records, whitelist changes, chain transfers, event-contract trades or tokenized-asset decisions become material.

3. Attestation

Attestation is the part of the decision where a public source has to become an operating rule. In this package, it means attestation proves a protocol message condition, not every user outcome. The useful action is to verify attestation status before mint or receipt claims. The unresolved edge is attestation service incident state, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.

For an operator, attestation should be recorded before funds, account access, wallet recovery, API order flow, document exports, tax records, whitelist changes, chain transfers, event-contract trades or tokenized-asset decisions become material.

4. Asset identity

Asset identity is the part of the decision where a public source has to become an operating rule. In this package, it means native USDC and unsupported or bridged tokens can differ materially. The useful action is to match ticker, contract and Circle-supported route. The unresolved edge is wallet UI labeling, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.

For an operator, asset identity should be recorded before funds, account access, wallet recovery, API order flow, document exports, tax records, whitelist changes, chain transfers, event-contract trades or tokenized-asset decisions become material.

5. Recipient state

Recipient state is the part of the decision where a public source has to become an operating rule. In this package, it means recipient balance display can lag protocol completion. The useful action is to confirm final address and destination transaction evidence. The unresolved edge is wallet indexing delay, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.

For an operator, recipient state should be recorded before funds, account access, wallet recovery, API order flow, document exports, tax records, whitelist changes, chain transfers, event-contract trades or tokenized-asset decisions become material.

6. Recovery path

Recovery path is the part of the decision where a public source has to become an operating rule. In this package, it means unsupported routes may not have a self-service recovery path. The useful action is to define support and escalation before sending material value. The unresolved edge is case-specific support outcome, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.

For an operator, recovery path should be recorded before funds, account access, wallet recovery, API order flow, document exports, tax records, whitelist changes, chain transfers, event-contract trades or tokenized-asset decisions become material.

7. Stop rule

Stop rule is the part of the decision where a public source has to become an operating rule. In this package, it means stop when chain support, attestation or recipient evidence is unclear. The useful action is to do not retry by sending more funds. The unresolved edge is future protocol upgrades, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.

Known Unknowns

• chain reorg or finality assumptions
• new chain rollout timing
• attestation service incident state
• wallet UI labeling
• wallet indexing delay
• case-specific support outcome
• future protocol upgrades

Practical Takeaway

The safest version of this article is the one that stays boring and exact. Circle CCTP is a cross-chain USDC transfer protocol, but a successful message flow should not be treated as a universal asset-recovery or chain-support guarantee. Current Circle documentation routes CCTP guidance through the Cross-Chain Transfer Protocol page, describes technical message and attestation workflows in the CCTP technical guide and separately lists supported chains and currencies for Circle Mint and related APIs. The decision outcome is to verify source chain, destination chain, message hash, attestation status, supported asset, wallet route, final recipient and recovery path before treating a cross-chain movement as complete. The user outcome is a clearer next inspection step, not a promise that a platform, API, transfer route, report, market contract or tokenized asset will work under every future condition.