cctp

CLI for Circle CCTP transfers, focused on EVM flows.

Status

Implemented commands:

• cctp chains
• cctp estimate
• cctp attestation
• cctp status
• cctp burn
• cctp claim
• cctp bridge
• cctp reattest

Current execution scope:

• EVM -> EVM
• EVM -> Solana burn
• EVM -> Solana claim
• EVM -> Solana bridge
• Solana -> EVM burn
• Solana -> EVM claim
• Solana -> EVM bridge
• CCTP v2-style execution path
• EVM signer loading via foundry-wallets::WalletOpts
• Solana signer loading via mnemonic + account index

Not supported yet:

• Solana destination burn/bridge orchestration from EVM source
• non-EVM destination execution beyond the Solana claim path
• broad chain coverage beyond the configured USDC metadata set

Build

With Cargo

cargo build

With Nix dev shell

nix develop
cargo build

Common commands

List supported chains:

cargo run -- chains
cargo run -- chains --testnet

Estimate fees:

cargo run -- estimate --from base-sepolia --to arbitrum-sepolia --amount 10

Query attestation:

cargo run -- attestation --from base-sepolia --tx 0x...

Check status:

cargo run -- status --from base-sepolia --tx 0x...

Burn:

cargo run -- burn \
  --source-chain base-sepolia \
  --destination-chain arbitrum-sepolia \
  --amount 1 \
  --recipient 0x... \
  --private-key 0x... \
  --rpc-url https://...

Solana -> EVM burn:

cargo run -- burn \
  --source-chain solana-devnet \
  --destination-chain base-sepolia \
  --amount 1 \
  --recipient 0x... \
  --solana-mnemonic "..." \
  --solana-account-index 0 \
  --solana-token-account <SPL_TOKEN_ACCOUNT> \
  --rpc-url https://api.devnet.solana.com

EVM -> Solana burn:

cargo run -- burn \
  --source-chain base-sepolia \
  --destination-chain solana-devnet \
  --amount 1 \
  --recipient <SOLANA_RECIPIENT_TOKEN_ACCOUNT> \
  --private-key 0x... \
  --rpc-url https://...

Claim:

cargo run -- claim \
  --source-chain base-sepolia \
  --destination-chain arbitrum-sepolia \
  --tx 0x... \
  --private-key 0x... \
  --rpc-url https://...

Solana -> EVM claim:

cargo run -- claim \
  --source-chain solana-devnet \
  --destination-chain base-sepolia \
  --tx <SOLANA_BURN_SIGNATURE> \
  --private-key 0x... \
  --rpc-url https://...

EVM -> Solana claim:

cargo run -- claim \
  --source-chain base-sepolia \
  --destination-chain solana-devnet \
  --tx 0x... \
  --solana-mnemonic "..." \
  --solana-account-index 0 \
  --rpc-url https://api.devnet.solana.com

Bridge end-to-end:

cargo run -- bridge \
  --source-chain base-sepolia \
  --destination-chain arbitrum-sepolia \
  --amount 1 \
  --recipient 0x... \
  --private-key 0x... \
  --rpc-url https://...

Solana -> EVM bridge:

cargo run -- bridge \
  --source-chain solana-devnet \
  --destination-chain base-sepolia \
  --amount 1 \
  --recipient 0x... \
  --solana-mnemonic "..." \
  --solana-account-index 0 \
  --solana-token-account <SPL_TOKEN_ACCOUNT> \
  --private-key 0x... \
  --rpc-url https://api.devnet.solana.com

EVM -> Solana bridge:

cargo run -- bridge \
  --source-chain base-sepolia \
  --destination-chain solana-devnet \
  --amount 1 \
  --recipient <SOLANA_RECIPIENT_TOKEN_ACCOUNT> \
  --private-key 0x... \
  --solana-mnemonic "..." \
  --solana-account-index 0 \
  --rpc-url https://...

Request re-attestation:

cargo run -- reattest --from base-sepolia --nonce 0x...

Wallets

Execution commands use Foundry wallet options through foundry-wallets. That means you can use familiar flags like:

• --private-key
• --mnemonic
• --keystore
• --account
• --ledger
• --trezor
• --from

Run command help to see the full set:

cargo run -- burn --help

Output

Most read-only and execution commands support:

• human-readable output by default
• --json for machine-readable output

CI

GitHub Actions runs:

• cargo fmt --all --check
• cargo clippy --workspace --all-targets -- -D warnings
• cargo build --workspace --locked
• cargo test --workspace --locked

Notes

• RPC URLs default from built-in chain metadata when available, or can be overridden with --rpc-url.
• Some chains listed by chains are read-only only until their execution metadata is wired in.
• Execution uses canonical Iris message+attestation data for claim flows.