Map CCTP burn, attestation and mint states before claiming USDC arrived

A cross-chain transfer is a sequence of independently observable states

CCTP moves native USDC by burning on a source chain and minting on a destination chain after a message is attested and relayed. A wallet may summarize that sequence as one transfer, but troubleshooting requires the source transaction, message and destination transaction to remain distinct. This is a verification and record-keeping method, not a prediction, payment instruction, legal opinion or promise of an account outcome.

Circle's technical guide explains the CCTP message flow and contracts. It does not state that SignalBet accepts CCTP, any destination chain or a bridged payment route. Readers tracing cross-chain USDC need to know which step succeeded and which identifier belongs to each chain.

Verify the route before initiating

A CCTP route includes a source domain, destination domain, token messenger contracts and a recipient encoded for the destination. That source-backed detail answers only this checkpoint. Protocol capability does not prove that the receiving service supports the route. The worksheet therefore carries the date and provenance forward without turning them into certainty.

Compare chain, native USDC contract and destination acceptance with current official documentation. The audit line captures source chain, destination chain, token contracts, recipient, service support evidence and time so another person can repeat it. It remains open whenever do not infer support from a wallet's route suggestion.

Record the source-chain burn transaction

The source transaction requests a deposit for burn and emits message-related data when successful. That source-backed detail answers only this checkpoint. A source-chain receipt proves only the outcome on that source chain. The worksheet therefore carries the date and provenance forward without turning them into certainty.

Capture the source hash, receipt and decoded burn amount. The audit line captures source hash, block, receipt status, USDC contract, amount, destination domain and message event so another person can repeat it. It remains open whenever do not call the burn a destination credit.

Derive and preserve the message identifier

The cross-chain message links the burn intent to later attestation and destination processing. That source-backed detail answers only this checkpoint. A wallet activity ID may not be the same as the protocol message hash. The worksheet therefore carries the date and provenance forward without turning them into certainty.

Use the documented tooling or trusted interface to record the message bytes or hash metadata. The audit line captures message hash, nonce, source domain, destination domain, sender and recipient encoding so another person can repeat it. It remains open whenever do not paste signing secrets into a message-status site.

Treat attestation as an intermediate state

Circle's attestation service signs eligible messages before they can be received on the destination chain. That source-backed detail answers only this checkpoint. An available attestation does not itself show that minting occurred. The worksheet therefore carries the date and provenance forward without turning them into certainty.

Record attestation availability and its retrieval source separately. The audit line captures message hash, attestation status, retrieval time, source origin and error response so another person can repeat it. It remains open whenever do not pay a stranger to release an attestation.

Confirm the destination-chain mint

The destination transaction submits the message and attestation to mint native USDC to the encoded recipient. That source-backed detail answers only this checkpoint. Destination receipt status and token events establish whether mint execution succeeded. The worksheet therefore carries the date and provenance forward without turning them into certainty.

Capture the destination hash, receipt and USDC transfer or mint event. The audit line captures destination hash, block, receipt, token contract, recipient, amount and event so another person can repeat it. It remains open whenever stop if the recipient or contract differs from the planned route.

Separate wallet arrival from account credit

A destination wallet balance can update while a service invoice remains unsupported, expired or unmatched. That source-backed detail answers only this checkpoint. Protocol completion and SignalBet account credit are different ledgers. The worksheet therefore carries the date and provenance forward without turning them into certainty.

Reconcile the destination event with the authenticated invoice and one support case. The audit line captures wallet balance change, destination event, invoice ID, account status, case number and decision so another person can repeat it. It remains open whenever do not send another cross-chain transfer to test support.

What the named source establishes and leaves unresolved

Circle's technical guide provides the burn-and-mint sequence, message domains and attestation role needed to distinguish each CCTP state. The map keeps protocol evidence separate from service acceptance.

Circle cannot authenticate a SignalBet route, guarantee attestation timing, approve a destination network or recover an unsupported deposit. CCTP interfaces and versions can change.

Close the record with a bounded decision

The status map records route validation, source burn, protocol message, attestation, destination mint, wallet balance and account credit with separate hashes and timestamps. No step is promoted into proof of the next.

SignalBet is for adults 18+ only where lawful. Cross-chain delays are not a reason to repeat a deposit, borrow money or chase a bet; pause until every ledger is reconciled.

Use the responsible-play centre, the editorial policy and the guide library for related safeguards.

Verify the route before initiating: Follow-up review

Treat the later observation as an additional layer. Keep source chain, destination chain, token contracts, recipient, service support evidence and time, compare the wording and explain any change. Protocol capability does not prove that the receiving service supports the route. Do not infer support from a wallet's route suggestion. The follow-up stores no password, one-time code, recovery code, seed phrase or private key and never treats an unresolved field as permission to continue.

Record the source-chain burn transaction: Follow-up review

Treat the later observation as an additional layer. Keep source hash, block, receipt status, USDC contract, amount, destination domain and message event, compare the wording and explain any change. A source-chain receipt proves only the outcome on that source chain. Do not call the burn a destination credit. The follow-up stores no password, one-time code, recovery code, seed phrase or private key and never treats an unresolved field as permission to continue.

Derive and preserve the message identifier: Follow-up review

Treat the later observation as an additional layer. Keep message hash, nonce, source domain, destination domain, sender and recipient encoding, compare the wording and explain any change. A wallet activity ID may not be the same as the protocol message hash. Do not paste signing secrets into a message-status site. The follow-up stores no password, one-time code, recovery code, seed phrase or private key and never treats an unresolved field as permission to continue.