USDC reaches Arc through Circle's Cross-Chain Transfer Protocol, which burns the USDC on the chain it leaves and mints fresh USDC on the chain it arrives at. Nothing is wrapped, nothing sits in a third-party escrow, and the balance that lands on Arc is the same asset Circle issues everywhere else.
Works on Arc testnet today; mainnet September 16, 2026.
Why does the bridging method matter on Arc?
On most chains, USDC is a passenger. On Arc it is the fuel: gas is paid in USDC at 18 decimals at the protocol level, and testnet fees have averaged about $0.004 per transaction. That makes the question "what exactly is the USDC on this chain?" operationally important rather than academic. A wrapped representation issued by a bridge is a claim on a bridge. Natively minted USDC is a liability of Circle, the same as the USDC in your exchange account.
Since Circle both issues USDC and built Arc, the native path is the intended one.
How does CCTP actually work?
Circle's Cross-Chain Transfer Protocol is a burn-and-mint design rather than a lock-and-wrap design:
- You deposit USDC into the CCTP contract on the source chain and specify Arc as the destination and a recipient address.
- The protocol burns that USDC on the source chain. It ceases to exist there.
- Circle's attestation service observes the burn and signs a message confirming it.
- That attestation is submitted on Arc, and the protocol mints an equal amount of native USDC to the recipient.
Supply is conserved across the two chains. There is no pool of locked collateral to drain, which is the failure mode that has produced most of the large bridge losses of the last several years.
What the flow looks like in practice
[SCREENSHOT: CCTP transfer form with Arc selected as the destination chain]
- Add Arc to your wallet first. You need the network present before you can select it as a destination or see the balance land. Chain ID, RPC and the exact fields are here.
- Choose the source chain. CCTP supports the major EVM networks where USDC is natively issued.
- Enter the amount and the destination address. Send to an address you control on Arc — normally the same EVM address you use elsewhere, since Arc uses standard EVM addressing.
- Approve, then transfer. Two transactions on the source chain: a token approval, then the burn.
- Wait for attestation. This is the step that takes real time; it is Circle's service confirming the burn, not a block confirmation.
- Receive on Arc. The mint completes and the balance appears. Verify it on the explorer rather than trusting the interface — how to read Arcscan.
Do you need gas on Arc before the USDC arrives?
This is the neat consequence of the fee design. Because gas on Arc is USDC, the asset you bridged in is your gas. There is no chicken-and-egg problem where you hold tokens you cannot move because you lack a separate native coin. Once USDC lands, you can transact.
On testnet you do not bridge at all — use Circle's faucet at faucet.circle.com to get test USDC directly. The testnet guide covers it.
What about mainnet timing?
Public mainnet opens on September 16, 2026. Circle has not published the mainnet chain ID, RPC endpoint or explorer host, and this hub will not guess them. Until those exist, all bridging practice happens on testnet with faucet funds.
When mainnet does open, the parameters will be published by Circle at arc.io and docs.arc.network. Verify them there — a bridging flow is exactly the context in which a typosquatted domain does the most damage, because you are pasting an address and signing an approval in the same sitting.
Safety checks worth running every single time
- Check the destination chain selector twice. A burn is irreversible; sending to the wrong destination is not a support ticket.
- Verify the URL character by character. Bridge interfaces are the most heavily typosquatted pages in crypto. Reach them from arc.io or circle.com, not from a search result or a message.
- Test with a small amount first. The fee cost of doing so on Arc is fractions of a cent, so there is no economic reason to skip it.
- Confirm the arrival on the explorer, not in the wallet UI. The explorer is the ledger; the wallet is a view of it.
Once the USDC is on Arc
You are ready for the actual work: deploying the token, locking the pool, and putting the team allocation on a schedule. Team Finance covers all of it — non-custodial since 2020, with more than $2.7 billion secured across 40,000+ projects on 26 chains.
Start with minting a token on Arc, then lock the liquidity.
Sources: docs.arc.network · Circle pressroom · Arcscan.
Last verified: August 2026