Skip to main content
The CCTP Prover settles intents using Circle’s own attestation infrastructure — the receiveMessage function that powers native CCTP transfers. Settlement security is identical to CCTP because settlement IS a CCTP transfer.

​
Architecture

​
How It Works

  1. Fulfillment: Solver fulfills the intent on the destination chain Portal
  2. Attestation request: The CCTP Prover dispatches a message through Circle’s MessageTransmitter
  3. Circle verification: Circle’s attestation service verifies and signs the message — the same process used for all native CCTP transfers
  4. Settlement: The source chain receives the attested message via receiveMessage and marks the intent as proven, allowing the solver to withdraw rewards

​
Security Model

The CCTP Prover inherits its security directly from Circle’s attestation service. There is no additional trust assumption beyond what a native CCTP transfer already requires — the prover is a thin wrapper that routes intent settlement through Circle’s existing infrastructure. This makes the CCTP Prover particularly suitable for regulated environments and institutional use cases where the trust model of the settlement layer must be well-understood and auditable.

​
Message Format

CCTP Prover uses the same standardized message format as other Eco bridge provers:
  • 8 bytes: Destination chain ID
  • 64 bytes per intent: [intentHash (32 bytes)][claimant (32 bytes)]

​
When to Use CCTP Prover

Ideal for:
  • Native USDC transfers where Circle’s attestation security is preferred
  • Institutional and regulated use cases requiring a well-established trust model
  • Flows that already involve CCTP (e.g., burn-and-mint USDC transfers)
For other cross-chain options, see: