bitpontBridge / Circle CCTP / Base
USDC · Base → Arbitrum · Circle CCTP on Base
Native USDC burn, attestation and destination mint.
Transfer native 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.
THIS ROUTE
USDC · Base → Arbitrum
USDC amounts and the maximum fee use USDC units. An unavailable fee estimate is not zero.
Contract identity & reference data
- Network
- Base
- Source
- Base
- Destination
- Arbitrum
- Asset
- Native USDC
- Settlement
- Burn → attest → mint → verify
Configured route identity. Current balances, liquidity and transaction permissions are checked before review on this page.