BITPONT / CIRCLE CCTP / NATIVE USDC

One asset.
Across your networks.

Transfer native USDC between Ethereum, Base and Arbitrum. Review a fee cap, track the source burn, receive the attestation and verify the destination mint inside Bitpont.

Circle CCTP V2Standard finalitySame wallet recipient

A source burn and destination mint are separate transactions. Keep ETH on both networks for fees.

Transfer native USDC

USDC

Your transfers & recovery

Recovery validates the source transaction, recipient, USDC amount and fee cap. It does not create another burn.

Wallet transactions

Receive USDC, then choose what comes next.

Select Use delivered USDC on a completed transfer. Bitpont rechecks finalized delivery, the receiving network and your current balance, then lets you prepare a swap, another transfer or an eligible lending deposit. Each next action has its own review and wallet approval.

Plan a supported capital move →
Is this bridged USDC or native USDC?

CCTP burns Circle-issued USDC on one network and mints native USDC on the other. This flow does not transfer USDC.e or other bridged representations.

What if minting was interrupted?

Keep the source hash. Recover the same burn and check any pending destination transaction before retrying. A consumed message needs finalized delivery evidence; it is not treated as an empty balance.

Are all networks or destination actions supported?

This interface supports Ethereum, Base and Arbitrum with standard finality, the same wallet recipient and no destination hook. It does not make cross-chain operations atomic.