Moving Stablecoins Across Chains: CCTP, Native and Bridged USDC

Introduction

Open a wallet on Arbitrum One and you may find two tokens with USDC in their names. Arbitrum's own documentation, read on 19 October 2026, lists them as two different tokens with two different contract addresses: native USDC and bridged USDC, whose symbol is USDC.e. The difference decides who stands behind the token you hold, and it is set at the moment you move USDC from one chain to another.

So moving a stablecoin between chains is never a neutral step. The route you choose decides whether you arrive with USDC that Circle issued on the destination chain, or with a token that a bridge minted there against USDC it holds somewhere else. Through Circle's CCTP, the first kind travels by burn-and-mint. The second travels by lock-and-mint, and it depends on the bridge for as long as you hold it.

Bridges are also where a large share of hacked money goes missing. Our calculation from DefiLlama's hacks database, read through its public API on 19 October 2026, puts incidents flagged as bridge hacks at 30.9% of the value hacked between 19 October 2025 and 18 October 2026: $764.2 million of $2,470.6 million, across 51 bridge-flagged records. The incident record itself, with its causes and dates, is set out in our guide to bridge hacks, so this page does not repeat it.

This page is written for someone who already holds USDC, or is about to, and needs it on a different chain. That might be to use an app on a layer-2 network, to pay someone who works on another chain, or to move savings off an exchange into a wallet of their own. If the idea of a bridge is new to you, our guide to how bridges work explains it first.

The sections below take the questions in the order you are likely to meet them. First comes the difference between native and bridged USDC, then how CCTP burns USDC on one chain and mints it on another, what its Standard and Fast options cost in time and fees, and which chains Circle supports today. After that come USDC.e and how a bridged token can become native USDC, the xERC20 proposal for other tokens, and the exchange path: withdrawing straight to the network you need.

Every figure on this page carries the date it was read and the source it came from, and every source was read on 19 October 2026. Chain lists, fees and timings change often, so check the source again before a large transfer. Nothing here is a recommendation to buy or hold any stablecoin, and no route described below removes risk; each one moves the risk to a different place.

Native and Bridged USDC: Same Name, Different Token

Two tokens can share a name and a price on a quiet day and still be different assets. The test is who issued the token on the chain where you hold it, and what has to keep working for it to stay worth a dollar.

Who issues each token

Native USDC is the token that Circle issues itself. Circle publishes the contract address of the USDC it issues on each supported chain, and that address list, read on 19 October 2026, is the reference for what counts as native USDC. On X Layer, for example, Circle's list describes the listed address as Circle-issued native USDC. A token at an address outside that list is something else, whatever it is called.

Native issuance answers the bridge question, not every question. How Circle backs USDC with reserves is covered in our stablecoins guide, and what can still push a stablecoin off its dollar peg is covered in our guide to stablecoin depeg risk.

Bridged USDC is a different product. Circle's Bridged USDC Standard, published in its stablecoin-evm repository on GitHub and read on 19 October 2026, says that bridged forms of USDC are subject to certain risks and are not issued by Circle. On X Layer, Circle's address list names a separate bridged token labelled USDC.e and says that it is not issued or backed by Circle (read 19 October 2026).

What backs a bridged token

A bridged token is built by lock-and-mint. You deposit native USDC into a bridge's smart contract on the origin chain, the bridge confirms the deposit on the destination chain, and a token contract there mints the same amount of its own token. Arbitrum's documentation, read on 19 October 2026, describes its own canonical bridge for USDC in these terms and calls the result Bridged USDC, with the symbol USDC.e.

The bridged token is a claim on the locked deposit. Circle's Bridged USDC Standard makes the link explicit: before any upgrade, the bridge must be able to pause bridging and lock the bridged supply, so that it is fully backed by native USDC held on the source chain (read 19 October 2026). The backing therefore sits in a contract you do not control, on a chain you may never visit.

Why bridged USDC exists at all

Bridged USDC often arrives first. A new chain can have a dollar token as soon as a bridge connects it to Ethereum. Native issuance depends on Circle's decision and on the due-diligence review that, according to Circle's Bridged USDC Standard, every target chain must pass (read 19 October 2026). The standard itself exists so that a chain can start with bridged USDC and keep a route to native issuance open.

The same logic works in reverse. On a chain where Circle issues no USDC, any token called USDC is either a bridged version or an imitation, whatever its label says, and the questions in this section apply to all of it. On a chain where Circle does issue USDC, both kinds can sit side by side, which is how a wallet comes to show two tokens with nearly the same name.

Where the difference shows

On an ordinary day you may not notice which kind you hold. The difference shows when the bridge fails. If the locked USDC leaves the bridge contract, or the bridge stops honouring withdrawals, the bridged token keeps its name and its balance in your wallet, while the deposit behind it may be gone.

Native USDC carries a different set of dependencies. It still relies on Circle as the issuer and on Circle's reserves, but a bridge adds no second dependency on top. Holding USDC.e means holding two exposures at once: the issuer's, through the USDC locked behind it, and the bridge's, through the contract that holds the lock. Holding native USDC means holding only the first, which is why the route you take matters more than the ticker you see.

How CCTP Moves USDC: Burn, Attest, Mint

Circle's Cross-Chain Transfer Protocol is the route that keeps USDC native from one end to the other. Circle's documentation, read on 19 October 2026, describes CCTP as a permissionless onchain utility that natively transfers USDC across blockchains by burn-and-mint, without traditional bridge liquidity pools. Any app can build on its contracts, but the signature in the middle of each transfer comes from Circle alone.

Step one: the burn on the source chain

A transfer starts on the chain you are leaving. According to Circle's technical guide, read on 19 October 2026, the sender calls a contract named TokenMessengerV2, which burns the USDC through a minter contract and then sends a message through a second contract, MessageTransmitterV2. The message records the amount, the destination, the recipient and the maximum fee the sender will accept.

Once that transaction confirms, the USDC no longer exists on the source chain. Nothing sits locked and waiting for you there; what remains is a message, and the transfer now rests on Circle signing it.

Step two: Circle's attestation

Circle's off-chain attestation service, which its documentation calls Iris, watches for the burn and signs the message once the source chain has reached the finality level that the sender asked for (technical guide, read 19 October 2026). The current version defines two levels: confirmed, used by Fast Transfers, and finalised, used by Standard Transfers. The signed message is the attestation, and an app collects it from Circle's API.

The burn's transaction hash is the key to that lookup. Circle's technical guide, read on 19 October 2026, says the API returns the message and its attestation for a given transaction hash, which is also how a stalled transfer is found and finished later. Keep the hash of any burn you make until the USDC has arrived.

Step three: the mint on the destination chain

On the destination chain, the message and its attestation are submitted to MessageTransmitterV2, and new USDC is minted to the recipient (technical guide, read 19 October 2026). Circle's Forwarding Service page, read the same day, says that a transfer without that service needs a wallet able to sign on both chains and native tokens to pay gas on both.

Some apps hand the last step to Circle's Forwarding Service, which broadcasts the mint for you. Circle's Forwarding Service fee table, read on 19 October 2026, lists a service fee of $0.05 per transfer for most destinations, charged in USDC on top of the destination gas and any CCTP protocol fee.

A Fast Transfer that stalls between the burn and the mint is not lost by default. Circle's technical guide, read on 19 October 2026, says the attestation service encodes an expiration block about 24 hours ahead in a current-version burn message before signing it. Circle's technical guide adds that an expired Fast Transfer burn can be signed again at any time while the burn transaction still exists on the source chain.

What CCTP asks you to trust

CCTP removes the pool of locked USDC that a lock-and-mint bridge has to guard, but it does not remove trust. The burn and the mint happen on-chain, while the step between them is Circle's signature. A transfer therefore depends on Circle's attestation keys and service, on the CCTP contracts, and on Circle as the issuer of the USDC at both ends.

Circle's technical guide, read on 19 October 2026, lists an API endpoint that returns the public keys for validating attestations, so an app can check that a message was signed by Circle before it submits the mint. The destination contract mints only when a message arrives with Circle's attestation, so the private key behind that signature, and the service that uses it, sit at the centre of CCTP's trust model.

Circle's technical guide, read on 19 October 2026, says the CCTP contracts were audited by ChainSecurity and OtterSec, and that the version with the Standard Transfer fee switch was audited by ChainSecurity. An audit narrows the risk in the code it covers, but it is no proof that the code is safe. For a USDC holder, the main gain is that the transfer adds no second party between you and the issuer you already rely on.

Standard and Fast Transfers: Time and Cost

The current version of CCTP offers two speeds. The difference is how long Circle waits before it signs, and that wait is set by the source chain rather than the destination.

Standard Transfer: wait for finality

A Standard Transfer is signed after hard finality, when the burn is unlikely to be reversed by a chain reorganisation (Circle's finality page). On 19 October 2026, Circle's finality page put the average Standard Transfer wait at about 15 to 19 minutes from Ethereum, Arbitrum, Base, OP Mainnet, Unichain and World Chain, about 25 seconds from Solana, about 8 seconds from Avalanche and Polygon PoS, and far longer from two chains: about 6 to 32 hours from Linea and about 2 to 4 hours from Starknet.

Circle's finality page ties the Starknet wait to the posting of its zk-rollup proof on Ethereum, and describes Linea's finality period as longer than that of other layer-2 chains.

The waits differ because chains reach finality in different ways: Circle's finality page says layer-2 chains built on Ethereum depend on when their batches are posted to Ethereum and finalised there, while Solana uses a different finality model. On Solana, Circle's finality page says a Standard Transfer waits for 32 blocks, about 25 seconds, while a Fast Transfer waits for votes from validators representing over two-thirds of the total stake, about 8 seconds (read 19 October 2026).

Circle's fee table, read on 19 October 2026, showed 0 basis points for Standard Transfers from every source chain it listed. You still pay gas for the burn and for the mint, and Circle says that its fees can change at any time.

Fast Transfer: pay for speed

A Fast Transfer is signed once the burn is confirmed in a block, typically within seconds (Circle's finality page). On 19 October 2026, Circle's finality page gave a Fast Transfer attestation time of about 8 seconds from Arbitrum, Base, OP Mainnet and Solana, and about 20 seconds from Ethereum, and its supported-chains page marked Avalanche and Polygon PoS, whose standard wait is already short, as offering no Fast option as a source.

The speed has a price. Circle's fee table, read on 19 October 2026, listed Fast Transfer fees of 1 basis point from Ethereum and Solana, 1.3 from Base and OP Mainnet, 1.4 from Arbitrum, 12 from Starknet and 13 from Linea. Circle's fee page says the fee is deducted from the amount when the USDC is minted, unless it is paid upfront on the source chain. On a transfer of 1,000 USDC, 13 basis points comes to 1.30 USDC, the top of the $0 to $1.30 per $1,000 range Circle's fee page states.

Linea shows the trade-off at its sharpest. On Circle's tables for 19 October 2026, a Standard Transfer from Linea waited about 6 to 32 hours at no Circle fee, while a Fast Transfer from Linea cost 13 basis points, the highest rate listed, and was signed in about 8 seconds.

Fast Transfers also draw on a global allowance, which Circle's finality page says exists to limit the risk of chain reorganisations while burns have not yet reached hard finality. Circle's fee page advises high-volume applications to switch to a Standard Transfer when that allowance runs low, and warns that a transfer whose maximum fee falls below the current rate may be degraded to a Standard Transfer.

Version 1 is being retired

Older integrations may have been built on the first version of the protocol, which Circle now calls CCTP V1 (Legacy) and which supports Standard Transfers only. Circle's migration guide, read on 19 October 2026, says the deprecation of version 1 begins on 31 October and completes on 1 December 2026, with message limits tightening until no new burns can start.

The same guide says users will not lose access to funds during the phase-out, and that all pending redemptions will remain available. Noble, a Cosmos chain, is the one chain that Circle's supported-chains page listed as running on version 1 only, and Circle's status page said on 19 October 2026 that, beginning 13 October, Circle is discontinuing support for USDC and CCTP V1 on Noble in a phased transition. If an app you use for USDC transfers has not said which version it runs, ask before you send.

Where CCTP Runs on 19 October 2026

Circle's supported-chains page, read on 19 October 2026, lists 31 blockchains for the current version of CCTP: Aptos, Arbitrum, Arc, Avalanche, Base, BNB Smart Chain, Codex, Cronos, EDGE, Ethereum, HyperEVM, Injective, Ink, Linea, Monad, Morph, OP Mainnet, Pharos, Plasma, Plume, Polygon PoS, Sei, Solana, Sonic, Starknet, Stellar, Sui, Unichain, World Chain, X Layer and XDC.

On 19 October 2026, Circle's supported-chains page said USDC is supported on every CCTP domain except BNB Smart Chain, which it lists for USYC only, so USDC can move by CCTP across 30 of the 31 listed chains. Every listed chain can receive a transfer, but the options differ by chain: Circle's supported-chains page, read on 19 October 2026, marks Fast Transfer as available from 15 of them as a source and the Forwarding Service as available to 20 as a destination.

Native is not the same as connected

Circle issues native USDC on more chains than CCTP connects. Its USDC address list, read on 19 October 2026, includes Algorand, Celo, Hedera, NEAR, Polkadot Asset Hub, XRPL and ZKsync Era, and none of those seven appears on the CCTP list that day. USDC there is still issued by Circle, but moving it to another chain needs a different route, such as an exchange that supports both networks.

Check the address, not the ticker

The name and symbol in a wallet are set by whoever deployed the token, so they prove nothing on their own. The contract address does. Arbitrum's documentation, read on 19 October 2026, gives native USDC on Arbitrum One the address 0xaf88d065e77c8cC2239327C5EDb3A432268e5831 and USDC.e the address 0xff970a61a04b1ca14834a43f5de4533ebddb5cc8, and Circle's own list gives the same native address.

Before you send or accept USDC on a new chain, compare the token's contract address with Circle's list for that chain. If the address is missing from Circle's list, the token is something other than native USDC, whatever its name says.

EURC, the euro version

Circle's euro stablecoin, EURC, also moves by burn-and-mint, but through a separate layer that Circle calls CCTP for non-USDC. Circle's CCTP overview, read on 19 October 2026, says that layer takes its fee in the source chain's gas token rather than deducting it from the amount. That matters if you hold EURC but no gas token on the chain you are leaving.

The same layer also carries tokens that Circle does not issue. Circle's CCTP overview, read the same day, says it supports permissionless wrapping of third-party assets, including pre-registered tokens such as WETH, so a Circle route alone is no proof that a token arrives native. The question to ask is always who issues the token on the chain where it lands.

USDC.e and Other Bridged USDC

What the .e means

Circle's naming guidance for bridged tokens, set out in its Bridged USDC Standard and read on 19 October 2026, suggests the token name Bridged USDC followed by the deploying team's name in brackets, and the symbol USDC.e. The document says that this form is common because USDC is often bridged from Ethereum to a new destination chain.

On Arbitrum One the name tells a short history. Arbitrum's documentation, read on 19 October 2026, says that Circle launched native USDC there in 2023 and added CCTP. Arbitrum's documentation says the symbol of the bridged token was then renamed USDC.e to accommodate a migration of liquidity to native USDC across the ecosystem. The same page expects that migration from USDC.e to USDC to continue over time.

The risk you inherit

Holding USDC.e adds a bridge to the list of things that must keep working. Its backing is the native USDC locked in the bridge contract on the origin chain. The security of that contract, the keys or governance that can upgrade it, and the system that verifies the bridge's messages therefore all stand behind your balance.

Exchanges are part of the picture as well. Arbitrum's comparison table, read on 19 October 2026, lists "CEX Support, directly redeemable 1:1 for U.S. dollars" as the benefits of native USDC and leaves the same row empty for USDC.e. OKX's withdrawal page, read on 19 October 2026, shows Polygon (USDC.e) as a network of its own, separate from its plain Polygon entry.

Who holds the controls

USDC contracts carry administrative roles, and on a bridged token someone other than Circle holds them. Circle's Bridged USDC Standard, read on 19 October 2026, names the token contract's roles as Owner, MasterMinter, Pauser, Rescuer and Blacklister, plus a ProxyAdmin that can upgrade the contract. The standard leaves it to the team behind a bridged token to secure and manage those roles until any upgrade, whether in a single key, a smart contract such as the bridge, or something else.

Those roles decide who can mint, pause or freeze the token, and the ProxyAdmin decides whether its code can be replaced. On native USDC they sit with Circle as the issuer, and the standard moves them to a Circle-owned address only at an upgrade. Until then they sit with the bridged token's team, so that team's key management becomes part of what you trust.

If you hold USDC.e

You have three choices, and each one fits some holders and not others.

• Keep it, if the app you use is built around it and you accept the bridge risk for as long as you hold it.
• Swap it for native USDC on a decentralised exchange on the same chain, after checking the quoted rate, the depth of the pool and the slippage before you confirm.
• Send it back through the bridge that issued it, which releases native USDC on the origin chain. On Arbitrum One that means the canonical bridge, for which Arbitrum's documentation gives a challenge period of about 6.4 days and a typical wait of about 7 days before the withdrawal can be claimed on Ethereum (read 19 October 2026).

Whichever you choose, do it before you need the money in a hurry. A bridged token is easiest to exit while the bridge and the markets around it are working normally.

Two other pages help with the detail. How canonical bridges, withdrawal windows and network fees work on the main layer-2 networks is covered in our guide to layer-2 fees and bridging. Whether a swap or a bridge transfer counts as a taxable event where you live is a separate question, covered in our guide to taxable events in swaps and bridges.

How Bridged USDC Becomes Native USDC

A bridged token does not have to stay bridged for ever. Circle's Bridged USDC Standard, read on 19 October 2026, is a specification for deploying bridged USDC on EVM chains. It is written so that Circle can later take over the token contract and turn it into native USDC, if Circle and the team behind the bridge both decide to do so.

The four steps in Circle's standard

The document, read on 19 October 2026, sets out the process in four steps:

• Bridge contracts. The chain's team deploys bridge contracts that can pause USDC bridging and burn the USDC they hold, or keeps the ability to add those functions later.
• Token contract. It deploys the bridged token from Circle's own USDC contract code, so that it matches native USDC on other EVM chains.
• The handover. If both sides decide to upgrade, the team pauses bridging, settles transfers in flight and hands the token contract's roles to Circle; the native USDC locked on the origin chain, equal to the bridged supply, is then burned, and Circle upgrades the token contract.
• The result. The upgraded contract keeps the existing supply, holders and app integrations, so holders keep their balances in the same token contract.

The standard is an option for Circle, not a promise to holders. Its first footnote, read on 19 October 2026, says the standard grants Circle the option, but not the obligation, to take ownership of the token contract and upgrade it, and that it cannot be applied after a bridged token has already been deployed. A second footnote says the target chain must pass Circle's own due-diligence review.

Linea: an upgrade in place

Linea, an Ethereum layer-2 network, announced on 5 March 2025 that it would be the first to upgrade from Circle's Bridged USDC Standard to native USDC (Linea blog, read 19 October 2026). Linea's announcement said the upgrade would need no action from users or developers and no swap of tokens. The same announcement, dated 5 March 2025, put the bridged USDC on Linea at over $21 million.

Circle's USDC address list, read on 19 October 2026, includes Linea among the chains where Circle issues USDC, and Circle's supported-chains page lists Linea for CCTP. For a holder, that is the whole point of the standard: the balance stays where it is, and what changes is who stands behind it.

Bridged tokens without that path

Because the standard cannot be applied after deployment, a bridged token launched without it has no in-place path to native USDC under that standard. The route left is a migration by holders. Arbitrum's documentation, read on 19 October 2026, describes exactly that for USDC.e on Arbitrum One: an ecosystem-wide liquidity migration to native USDC that it expects to continue over time.

ERC-7281 (xERC20): Issuer-Controlled Bridging

USDC has its own route because its issuer runs one. Issuers of other tokens face the same choice between bridges, and xERC20 is a proposal for giving them similar control. It was posted for discussion on the Ethereum Magicians forum on 7 July 2023 as ERC-7281, Sovereign Bridged Tokens, and its first post describes it as a minimal extension to the ERC-20 token standard (thread read 19 October 2026).

What the proposal sets out

The first post, read on 19 October 2026, lists three parts:

• A burn and mint interface on the token that only bridges allowlisted by the token's issuer can call.
• Rate limits that the issuer configures for those bridges, capping how much each one can mint and burn.
• A Lockbox, a simple wrapper contract on the token's home chain that holds the existing token, so that a token already in use can adopt the design.

In the proposal's own description, ownership of tokens shifts away from bridges and into the hands of token issuers. The first post gives a bridge hack as one case it addresses: if a bridge is compromised, the issuer's exposure is capped at that bridge's rate limit, and the issuer can remove the bridge without a migration for users. It named the Multichain hack of that same day as an example.

DefiLlama's hacks database, read through its public API on 19 October 2026, records the Multichain incident of 7 July 2023 at $126.0 million and classifies its technique as a validator key compromise.

Its status in October 2026

ERC-7281 is a proposal, not a finalised standard. Its pull request to the official ERC repository on GitHub, opened on 3 November 2023, was closed for inactivity on 18 June 2026 without being merged. The ERC website had no page for ERC-7281 when checked on 19 October 2026.

Tokens can use a proposed interface before it is accepted, so the status of the proposal says little about whether a given token uses it. The point for a holder is narrower. A token that uses xERC20 is only as safe as the bridges its issuer has allowlisted and the limits set for each, and the ticker will not tell you which bridges those are. The token's own documentation should.

The Exchange Path: Withdraw to the Chain You Need

If your stablecoins sit on a cryptocurrency exchange, the simplest route to another chain may involve no bridge at all. You withdraw directly to your wallet address on the destination network, and the exchange makes the transfer on that network. OKX's UK withdrawal-fee page, read on 19 October 2026, listed 13 networks for USDC withdrawals: Aptos, Arbitrum One, Avalanche C-Chain, Base, Ethereum (ERC20), Monad, Optimism, Polygon, Polygon (USDC.e), Solana, Sui, Unichain and X Layer, while its international page listed 14 that day, adding Arc. Our OKX exchange guide covers the account side, and you choose the network on the withdrawal screen.

The network you pick changes the cost. At 09:35 UTC on 19 October 2026, OKX's UK withdrawal-fee page listed a network fee of 0.72 USDC for Ethereum, 0.031 USDC for Base and 0.0052 USDC for Arbitrum One, and OKX says the fee depends on factors such as network congestion. OKX's minimum withdrawal on 19 October 2026 was 2 USDC on most networks.

Three checks before you confirm

• The network label matches the chain your destination wallet uses, word for word: on OKX's list, Polygon and Polygon (USDC.e) are two different routes.
• The receiving address is yours on that chain. EVM networks share one address format, which makes a wrong network easy to pick and hard to notice.
• A small test arrives first, as native USDC at the contract address that Circle lists for that chain, before you send the rest.

What the exchange path trades away

The exchange path swaps bridge risk for custody risk. While your USDC sits in an exchange account, the exchange holds it, and a withdrawal depends on the exchange processing it. Withdraw once you know where the money needs to go, rather than leaving a balance on the exchange for later.

Exchanges also decide which networks they support, and they can change them. OKX announced on 1 August 2024 that it would stop USDC deposits and withdrawals on its Optimism (Bridged) network on 5 August 2024, while keeping USDC on its other supported chains (OKX announcement, read 19 October 2026). A bridged version can lose exchange support while the native one keeps it.

Choosing a Route for Your Stablecoins

No single route suits every transfer. The choice depends on where the stablecoin is now, which token you need at the other end, and how long you can wait.

• Native USDC in your wallet, going to a chain on Circle's list: use an app or a bridge that moves it through the current version of CCTP, and check which version it runs, because Circle's migration guide, read on 19 October 2026, says version 1 is retired between 31 October and 1 December 2026.
• USDC on an exchange: withdraw straight to the destination network, if the exchange lists it.
• USDC.e or another bridged USDC: decide whether you need it at all; if you do not, swap it or return it through its bridge, as described above.
• A destination where Circle issues no native USDC: you will hold a bridge's version, so keep the amount and the time in proportion to the risk you accept.
• A stablecoin other than USDC: find out who mints it on the destination chain and what backs it there before you move it.

A worked example: 2,500 USDC from Ethereum to Base

Suppose you hold 2,500 native USDC on Ethereum and want it on Base. Through a CCTP Standard Transfer, Circle's tables read on 19 October 2026 show no Circle fee and an average wait of about 15 to 19 minutes for the attestation. You would also pay gas for the burn on Ethereum and for the mint on Base.

On Circle's fee table for 19 October 2026, a Fast Transfer from Ethereum cost 1 basis point, which is 0.25 USDC on this amount, with an attestation in about 20 seconds. If the same 2,500 USDC sat on OKX instead, its UK withdrawal-fee page listed a 0.031 USDC network fee for Base at 09:35 UTC on 19 October 2026, a fee OKX says depends on factors such as network congestion, and no bridge would be involved. Whichever route you take, check the token you receive against Circle's address list for Base.

Before you move a large amount

• Confirm what you hold. Match the token's contract address with Circle's list for that chain before you assume it is native USDC.
• Confirm the route. Check that the destination chain is on Circle's CCTP list, and which speed and fee the app you use will apply.
• Plan for gas on both chains. You need the native gas token to pay the gas fee on the destination chain, unless the app submits the mint for you.
• Send a small amount first, and wait until it arrives before you move the rest.
• Keep the burn's transaction hash until the transfer is complete, since it is how Circle's API finds the message and its attestation.

Fake bridge sites and approval traps

Whichever route you choose, reach it from an address you typed or bookmarked, never from a link in a message or an advert. A fake bridge page can ask for the same token approval and signature as a real one, so the address you used to reach it is the check that matters. Our crypto scam protection guide covers the checks to run before you sign anything.

If you are still deciding which network to hold stablecoins on in the first place, our comparison of Arbitrum, Optimism and Base sets out how the three networks differ.

Conclusion

The name on a token tells you less than the route it took. Native USDC on a chain is issued there by Circle. Bridged USDC, often labelled USDC.e, is a claim on USDC locked in a bridge, and it carries that bridge's risk for as long as you hold it.

CCTP keeps USDC native from one end to the other by burning it on one chain and minting it on another once Circle has signed the burn. It removes the locked pool that a lock-and-mint bridge must guard, and relies instead on Circle's attestation service and contracts. According to Circle's tables on 19 October 2026, Standard Transfers carried no Circle fee and waited for finality, while Fast Transfers cost between 1 and 13 basis points, depending on the source chain, and were signed within about 8 to 20 seconds.

For tokens already bridged, the way back to native USDC runs through Circle's Bridged USDC Standard where a chain adopted it, as Linea did, or through a migration by holders where it did not. For other tokens, ERC-7281 proposes issuer-set limits on each bridge, but on 19 October 2026 it remained a proposal.

If your stablecoins are on an exchange, withdrawing native USDC straight to the destination network avoids a bridge step of your own, at the cost of trusting the exchange while the money sits there. In every case the habits are the same: check the network label, then the contract address, and test with a small amount before the rest.

The figures here will age quickly. Circle adds chains, changes fees and retires versions, and exchanges add and drop networks. Before a large transfer, read Circle's supported-chains and fee pages and the exchange's withdrawal page again on the day, and treat every figure on this page as the value read on 19 October 2026.

None of these routes removes risk. Each one decides where the risk sits, and the right choice is the one whose risk you understand and are willing to hold for as long as the money stays there.

Sources

Every primary source below was read on 19 October 2026. Each entry names the document and what it supports on this page. The last entries point to the pages of this site that cover the neighbouring questions.

• Circle, Cross-Chain Transfer Protocol overview — CCTP as a permissionless burn-and-mint utility without bridge liquidity pools, its two transfer speeds, the EURC route and its fee model, and the wrapping of third-party assets. developers.circle.com
• Circle, CCTP supported blockchains and domains — the 31 listed chains, USDC on 30 of them, Fast Transfer and Forwarding Service availability, and Noble as the one chain on version 1 only. developers.circle.com
• Circle, CCTP finality and block confirmations — the attestation times for Standard and Fast Transfers by source chain, finality on Solana, and the purpose of the Fast Transfer allowance. developers.circle.com
• Circle, CCTP fees — the Fast and Standard Transfer fee tables, the 0 to 13 basis point range, the advice on a low allowance, and the warnings that fees can change and that a low maximum fee can degrade a transfer. developers.circle.com
• Circle, CCTP technical guide — the burn, attestation and mint steps, the finality thresholds, lookup by transaction hash, message expiry and re-attestation, the public keys for validating attestations, and the audits. developers.circle.com
• Circle, Forwarding Service for CCTP — gas on both chains without the service, and the service fee table. developers.circle.com
• Circle, Migrate from CCTP V1 (Legacy) to V2 — the deprecation timeline for version 1 and access to funds during the phase-out. developers.circle.com
• Circle status page, Circle is discontinuing support for USDC and CCTP V1 on Noble in a phased transition, posted 10 September 2026 — the phase-out on Noble beginning 13 October 2026. status.circle.com
• Circle, USDC contract addresses — native USDC addresses by chain, Circle-issued native USDC and the bridged USDC.e on X Layer, Linea, and the chains with native USDC outside the CCTP list. developers.circle.com
• Circle, Bridged USDC Standard, stablecoin-evm repository — the upgrade steps, the token roles, the naming guidance for USDC.e, and the footnotes on Circle's option, on due diligence and on bridged USDC not being issued by Circle. github.com
• Arbitrum documentation, USDC on Arbitrum One — the two USDC tokens and their addresses, the 2023 launch of native USDC, the renaming to USDC.e and the benefits table. docs.arbitrum.io
• Arbitrum documentation, Monitor withdrawals — the challenge period of about 6.4 days and the typical wait of about 7 days on Arbitrum One. docs.arbitrum.io
• Linea blog, announcement of the upgrade to native USDC, 5 March 2025 — the first upgrade from the Bridged USDC Standard, no swap for holders, and the bridged USDC on Linea at the time. linea.build
• Ethereum Magicians, ERC-7281: Sovereign Bridged Tokens, discussion opened 7 July 2023 — the proposal's three parts, its aim and the Multichain example. ethereum-magicians.org
• GitHub, ethereum/ERCs pull request 89, Add ERC: Sovereign Bridged Token — opened 3 November 2023 and closed for inactivity on 18 June 2026 without being merged. github.com
• DefiLlama, hacks database, read through its public API (last modified 19 October 2026, 06:36 UTC) — the bridge-flagged share of value hacked between 19 October 2025 and 18 October 2026, and the Multichain record of 7 July 2023. defillama.com
• OKX, Withdrawal fees and supported tokens (UK page) — the 13 USDC withdrawal networks, the network fees at 09:35 UTC and the minimum withdrawals; the international page adds Arc. okx.com
• OKX, announcement of 1 August 2024 on USDC deposits and withdrawals on the Optimism (Bridged) network — the end of that network on 5 August 2024. okx.com
• What a bridge is, the four ways bridges move value and the trust model behind each are on our bridges guide.
• Incidents by date, with their causes and what they teach, are on our bridge hacks guide.
• How stablecoins hold their value, and how USDC's reserves work, are on our stablecoins guide.
• What can push a stablecoin below a dollar, issuer risk included, is on our depeg risk guide.
• Canonical bridges, withdrawal windows and fees on the main layer-2 networks are on our layer-2 fees and bridging guide.
• The tax treatment of swaps and bridge transfers is on our taxable events guide.
• How Arbitrum, Optimism and Base differ as places to hold stablecoins is on our Arbitrum, Optimism and Base comparison.
• The checks to run before you sign anything on a bridge site are on our crypto scam protection guide.

Frequently Asked Questions

What is the difference between native USDC and bridged USDC?

Native USDC is issued by Circle on the chain where you hold it, and Circle publishes its contract address for that chain. Bridged USDC is minted by a bridge against native USDC locked on another chain, so its backing depends on that bridge as well as on Circle. Circle's Bridged USDC Standard, read on 19 October 2026, says bridged forms of USDC are subject to certain risks and are not issued by Circle.

What is USDC.e?

USDC.e is the symbol commonly given to USDC bridged from Ethereum to another chain, following the naming Circle suggests in its Bridged USDC Standard (read 19 October 2026). On Arbitrum One, Arbitrum's documentation describes USDC.e as Ethereum-native USDC bridged through its lock-and-mint bridge, at a different contract address from native USDC (read on 19 October 2026). Check the address against Circle's list before you treat a token as native USDC.

Can I convert USDC.e to native USDC?

Yes, in two ways: swap it on a decentralised exchange on the same chain, after checking the rate and the slippage, or send it back through the bridge that issued it to receive native USDC on the origin chain. On Arbitrum One, Arbitrum's documentation gives a typical wait of about 7 days before a canonical bridge withdrawal can be claimed on Ethereum (read 19 October 2026). Where a chain adopted Circle's Bridged USDC Standard, Circle and the chain's team can instead upgrade the token in place.

How long does a CCTP transfer take?

It depends on the source chain and the speed you choose. Circle's tables, read on 19 October 2026, gave about 15 to 19 minutes for a Standard Transfer from Ethereum, Arbitrum, Base and OP Mainnet, and about 8 to 20 seconds for a Fast Transfer from the chains that offer one. Circle's finality page, read on 19 October 2026, gave about 6 to 32 hours for a Standard Transfer from Linea and about 2 to 4 hours from Starknet.

Does CCTP charge a fee?

Circle's fee table, read on 19 October 2026, showed 0 basis points for Standard Transfers, and Fast Transfer fees in a range Circle gives as 0 to 13 basis points depending on the source chain, deducted when the USDC is minted. You also pay gas for the burn on the source chain, and for the mint on the destination chain unless an app uses Circle's Forwarding Service, which charges its own fee for that step. Circle says its fees can change at any time.

Which chains does CCTP support?

Circle's supported-chains page, read on 19 October 2026, listed 31 blockchains for the current version of CCTP and said USDC moves on all of them except BNB Smart Chain. They include Ethereum, Arbitrum, Base, OP Mainnet, Polygon PoS, Avalanche, Solana, Linea, Unichain and World Chain. Noble was listed only for the legacy version 1, and Circle's status page said on 19 October 2026 that, beginning 13 October 2026, Circle is discontinuing support for USDC and CCTP V1 on Noble in a phased transition.

What is xERC20?

xERC20 is the informal name of ERC-7281, a proposal first posted for discussion on 7 July 2023 that lets a token's issuer choose which bridges may mint and burn the token and cap each one with a rate limit. Its pull request to the official ERC repository was closed for inactivity on 18 June 2026 without being merged, so on 19 October 2026 it remained a proposal rather than a finalised standard.

Can I withdraw USDC from an exchange straight to a layer-2 network?

Often you can, if the exchange lists that network for USDC. OKX's UK withdrawal-fee page, read on 19 October 2026, listed 13 USDC networks, including Arbitrum One, Base, Optimism, Polygon, Unichain and X Layer, with a separate entry for Polygon (USDC.e), and its international page listed 14, adding Arc. Pick the network your wallet uses, send a small test first, and check the token's contract address when it arrives.

What happens to bridged USDC if its bridge is hacked?

The bridged token stays in your wallet, but the native USDC behind it may be gone, because its backing is the deposit locked in the bridge. How much holders get back, if anything, depends on the bridge and on what its operators do afterwards, and nobody can promise an outcome in advance. Native USDC moved through CCTP has no locked pool of this kind behind it.

Financial Disclaimer

This content is not financial advice. All information provided is for educational purposes only. Cryptocurrency investments carry significant investment risk, and past performance does not guarantee future results. Always do your own research and consult a qualified financial advisor before making investment decisions.