Native USDC Transfers: CCTP Burn, Attest & Mint

Set the source and destination

Connect the owning EVM wallet. Choose distinct supported networks and enter native USDC, not a bridged look-alike token. The same address receives the output. Inspect the current Circle fee and enter a maximum fee; the difference sets your minimum destination amount.

Approve, then burn

Review the exact USDC allowance and burn separately. A successful burn removes source USDC. It cannot be cancelled from Bitpont. Keep the source transaction hash and wait for canonical finality and the matching Circle attestation.

Mint on the destination

When claimable, switch to the destination network, keep ETH for gas and review the exact attested message. The transmitter rejects a message that has already been consumed. Bitpont verifies the message identity, destination domain, recipient, fee and nonce before preparing the mint.

Recover the same transfer

Import the source hash if local history is missing. If a mint submission is uncertain, check it before trying again. A consumed message needs its destination transaction hash to prove delivery. Retrying an earlier mint requires a valid matching finalized reverted transaction. Delivered requires both the matching received-message event and the exact USDC mint. After delivery, select Use delivered USDC to prepare an eligible swap, bridge or lending action. Bitpont checks fresh finalized proof and the current receiving balance first. Each next action has a separate review and wallet approval; there is no destination hook or automatic follow-on deposit.