CCTP on Hyperliquid
Circle's Cross-Chain Transfer Protocol moves native USDC between supported chains through issuer-controlled burn-and-mint infrastructure rather than creating a wrapped bridge token.
CCTP is Circle's canonical crosschain transport for native USDC. A transfer burns USDC on the source chain, obtains Circle attestation under the protocol, and mints native USDC on the destination. Hyperliquid support means users and applications can route USDC into or out of HyperEVM without depending on a separate wrapped-USDC liquidity pool for every supported source chain.
Burn and mint
The key accounting idea is supply relocation. USDC is destroyed on the source and created on the destination rather than locked in a third-party bridge contract while a derivative token circulates elsewhere.
CCTP versions
Circle states that CCTP V2 became the canonical CCTP and began phasing out V1. Builders should use the current contracts, domains, APIs, and finality options from Circle's documentation rather than old Hyperliquid tutorials.
Fast transfer and fees
CCTP can support different transfer modes or fee structures depending on route and version. Applications should expose expected timing and fees instead of advertising crosschain USDC as universally instant.
Failure model
CCTP reduces bridge-liquidity fragmentation but introduces reliance on Circle's contracts and attestation infrastructure. A crosschain transfer can also be operationally delayed even when Hyperliquid itself is healthy.
Application design
Track transfer state across source burn, attestation, destination mint, and final balance. Do not credit users solely from a source transaction hash before the destination state is confirmed.