PortalCCTP

The Problem

Cross-chain stablecoin movement is broken. Users face a fragmented landscape of third-party bridges, each with different security assumptions, liquidity constraints, and fee structures. Wrapped assets introduce counterparty risk. Liquidity pools can be drained. Settlement times vary from minutes to hours with no visibility into status.

Moving $10,000 in USDC from Arbitrum to Base should not require trusting an intermediary or accepting a synthetic asset.

The Solution

PortalCCTP builds directly on Circle's Cross-Chain Transfer Protocol v2. This is the only mechanism where USDC is burned on the source chain and minted natively on the destination. No wrapped tokens. No liquidity pools. No third-party custody.

The protocol flow is straightforward: burn USDC on Chain A, wait for Circle's attestation service to sign the message, mint USDC on Chain B. PortalCCTP abstracts these three steps into a single interface with real-time status tracking.

Technical Architecture

Protocol Layer

• Circle CCTP v2 MessageTransmitter and TokenMessenger contracts
• Circle Iris attestation service for cross-chain message verification
• Native burn/mint mechanism (no wrapped or synthetic assets)

Application Layer

• Non-custodial wallet integration (user signs all transactions)
• Automatic network detection and switching prompts
• Transaction indexing for burn/mint correlation

Finality Options

• Fast Mode: Pays priority fee to Circle's relayer network. Settlement in seconds.
• Standard Mode: Waits for natural attestation. Settlement in 10-15 minutes. No additional cost.

Supported Networks

Eleven mainnet deployments:

Additional networks added as Circle expands CCTP support.

Advanced Configuration

For programmatic integrations and power users:

• Destination Caller: Restrict mint execution to a specific address. Required for mint-and-call patterns.
• Hook Data: Attach arbitrary hex payload to the mint transaction. Enables downstream contract execution.
• Max Fee Override: Set explicit ceiling on fast-mode priority fees.

Security Model

PortalCCTP is a frontend. It does not custody assets, relay transactions, or operate infrastructure.

• All transactions signed locally in user's wallet
• Contract interactions limited to Circle's audited CCTP deployments
• Attestation verification handled by Circle's Iris service
• No backend servers, no API keys, no stored user data

The security boundary is Circle's protocol and the user's wallet. PortalCCTP adds no additional trust assumptions.

Development Status

Usage

1. Connect wallet
2. Select source chain, destination chain, amount
3. Select finality mode (fast/standard)
4. Approve USDC spend (first transfer only)
5. Execute burn transaction
6. Wait for attestation (status displayed in UI)
7. Switch to destination network
8. Execute mint transaction

Both transaction hashes displayed for verification.