USDC Bridge CCTP V1 Is Shutting Down: How to Check Whether Your Stablecoin Can Still Change Chain From December

If you hold USDC and have ever sent it from one blockchain to another, one date now belongs in your calendar: December 1, 2026. On that day the issuer Circle brings the old version of its official transfer bridge to a halt. Seven weeks earlier, on October 31, the caps on that bridge start to fall. Anyone holding USDC on the Cosmos chain Noble faces a separate, harder deadline: there, all contracts will be halted on January 12, 2027.

The short version first: for most retail investors practically nothing changes, because they keep their stablecoins on an exchange and the switch happens there in the background. Anyone who self-custodies, uses an older wallet app or holds USDC on Noble does have to act. This piece shows you which of the two groups you belong to, and how to establish that in a few minutes.

What Circle announced on September 10 and which two dates count

Circle issues USDC, the second-largest stablecoin by market value. The company also operates the Cross-Chain Transfer Protocol, or CCTP for short: the in-house mechanism by which USDC officially moves from one blockchain to another. That mechanism exists in two versions. The first, CCTP V1, has been classified as the legacy version since November 2025. The second, CCTP V2, is its successor.

On September 10, 2026, Circle went further and announced that it would discontinue USDC and CCTP on the Cosmos chain Noble entirely. Four dates are now fixed, and two of them concern every chain, not just Noble.

• October 13, 2026: no new USDC will be minted on Noble through Circle Mint.
• October 31, 2026: the shutdown of CCTP V1 begins. The caps for transfers fall step by step.
• December 1, 2026: the legacy version's contracts are halted. From this point nothing runs over CCTP V1 any more.
• January 12, 2027: on Noble, the USDC contract and all transfer routes are halted. Circle records a final snapshot of the remaining balances; from the following day a manual redemption through customer support is to be possible.

The key sentence in Circle's own description of the shutdown says, in substance, that the message caps tighten over time until no new transfers can be initiated. Volume therefore falls to zero before the contracts come to a final stop. In practice that means there is no single moment at which an error message appears. It gradually gets tight, and at some point nothing works at all.

CCTP explained: why USDC is burned and reminted when it changes chain

CCTP is a procedure in which the stablecoin is destroyed on the source chain and reissued in the same amount on the destination chain. Nothing is shifted back and forth, then: it is cleared away on one side and freshly created on the other. The technical term for this is burn and mint.

Why that matters becomes clear from the alternative. Classic bridges work differently: they lock your coins in a contract on the source chain and give you a claim ticket for them on the destination chain. That ticket is worth only as much as the locked holdings. If the contract is cracked, the ticket is worthless while the original coins sit with the attacker. Exactly this pattern lies behind a large share of the bridge losses of recent years.

With burn and mint there is no such ticket. The USDC that reaches you is genuine USDC, with the same claim against the issuer as any other. That is the reason wallets and trading venues have built this mechanism in, and at the same time the reason its shutdown is more than a footnote for developers.

Our own survey: how we checked chains, domains and the Noble balance

cryptoticker.io collected this data itself on September 11, 2026. The method in one sentence: we retrieved Circle's public developer documentation in its source form, counted the chains and domain identifiers listed there, and read out the actual USDC balance on Noble through two mutually independent node operators.

Objects checked: 30 rows of the chain table, 30 domain identifiers, two balance queries on Noble, plus one price query for the conversion into euros. All requests returned response code 200. The balance was read on Noble at 18:58 UTC at block height 59,047,213; both nodes reported the same figure to the decimal, which is a strong sign that neither of them was lagging behind.

A domain identifier is the number under which Circle lists a blockchain in its contracts. It has nothing to do with the public chain ID you know from your wallet and serves internal addressing alone.

29 chains with CCTP V2, two without a successor: Noble and Sui

The current chain table lists 30 entries, of which 29 are mainnets and one a testnet. All 29 mainnets support the standard transfer. With the additional functions the picture thins out: the fast transfer is available as a starting point on 15 chains, the pre-paid fee on 17, the forwarding service on 19. Anyone assuming the new version can do the same thing everywhere is wrong in roughly half the cases.

The names of the 29 mainnets range from the large and familiar ones such as Ethereum, Solana, Base, Arbitrum, OP Mainnet, Polygon PoS and Avalanche to chains most investors will never encounter. At the first mention it is worth the pointer: how Ethereum has developed as an underlying asset and which metrics matter there right now is set out in our Ethereum price prediction.

More interesting than those present are the absent. The legacy version CCTP V1 ran on eleven chains. Two of them are missing from the new version's table: Noble and Sui. For Sui, Circle has announced that it will add support before the shutdown begins. For Noble there is no such announcement; on the contrary, that is where the shutdown happens. It is also striking that the domain identifiers in the new table run from 0 to 37 while eight numbers are simply missing. That fits the finding that individual chains from the legacy version were given no place in the new one.

103.6 million USDC on Noble: the balance the clock is running on

How large is the balance still sitting on Noble? Our measurement on September 11, 2026 at 18:58 UTC produced exactly 103,643,460.117084 USDC, confirmed by two independent node operators. At a price of €0.862332 per USDC, retrieved the same day, that corresponds to roughly €89.4 million. The euro stablecoin EURC, also listed on Noble, stood at zero at the same moment.

That figure says nothing about who owns the balance. A considerable part of it is likely to sit with trading venues, protocols and institutional holders that have exit plans of their own. It does say a great deal about the order of magnitude, though: the amount runs into the hundreds of millions and is therefore far above anything that could be dismissed as a residual balance. It needs a new home by January 12, 2027.

Contradictory statements about Aptos in Circle's own documentation

While counting we came across an inconsistency, and it belongs in this piece because it can cost you a decision. The new version's chain table lists Aptos as supported, with the standard transfer and its own domain identifier. Elsewhere in the same documentation it says, in substance, that Noble, Sui and Aptos continue to require the legacy version.

Both cannot be true at once. Which of the two is more up to date cannot be settled from the outside, and we therefore make no claim that either one is wrong. For you a plain rule follows from it: when changing chain, rely on what the app you actually use displays at the moment of the transfer, rather than on a documentation page. If a route is offered there, it exists. If it disappears, the question has been answered.

Standard transfer: why CCTP V1 takes between 13 and 19 minutes

The standard transfer is the procedure in which Circle waits until the burn on the source chain is definitively irreversible and only then issues the approval for the mint. That definitiveness is known as hard finality. Circle puts the waiting time for it at around 13 to 19 minutes for Ethereum and the chains built on top of it.

The legacy version can do this one procedure and nothing else. The new version additionally supports the fast transfer, in which approval is issued earlier and the risk is carried by Circle, as well as so-called hooks, which allow a further action on the destination chain to be attached directly to a transfer. So if your chain switch regularly takes a quarter of an hour today, that is an indication that the app is still sitting on the legacy version.

Who is affected and who merely needs to note this article

The honest answer is relaxed for many readers. If your USDC sits in an account at an exchange, the switch concerns you only indirectly. The exchange moves balances between chains with its own technology, and migrating to the new version is a job for its engineering department rather than for you.

You do have to act if at least one of these points applies to you: you hold USDC on Noble or in a Cosmos wallet. You use a wallet or a swap interface that handles its chain switching over the legacy version and has had no update for months. Or you run something yourself that moves USDC between chains automatically.

For self-custody the switch is a good occasion to go through the whole setup once. Which wallet supports which chains, and where the differences lie, we have set side by side in the software wallet comparison. For Noble, Circle explicitly names Keplr and Cosmostation as wallets through which the balance remains reachable.

Coinbase cut off Noble USDC back in August

One detail from the coverage puts the timetable in perspective: Coinbase stopped deposits and withdrawals of USDC on Noble as early as August 17, 2026, a good three weeks before Circle's announcement. So anyone who had counted on simply handing their Noble balance to the largest American exchange has not had that route for weeks.

Circle itself names three ways out of Noble: depositing at a trading venue that still accepts Noble, swapping on a decentralised trading venue on Noble itself, or using the legacy version to have the balance reminted on one of the supported destination chains. Named for that are Aptos, Arbitrum, Avalanche, Base, Ethereum, OP Mainnet, Polygon PoS, Solana, Sui and Unichain. The third route has the tightest frame, because it ends on December 1, six weeks before the Noble deadline itself.

Checking your USDC balance: four steps in five minutes

The check is unspectacular and quickly done.

Step 1: Look up where your USDC actually sits

Open your wallet and see which chain the USDC balance is listed under. Many wallets show the same figure added up across several chains; you need the breakdown. If it says Noble or Cosmos, the January deadline applies to you.

Step 2: Call up the swap interface once without committing

Open the interface you normally use to change chain and enter a small amount without confirming. If you are shown a waiting time of around a quarter of an hour, it is working with the standard transfer. That is no problem in itself, but it is a reason to check the interface again after December 1.

Step 3: Test a small amount in advance

If you want to move a larger sum in November or December, send a small amount over the same route first. That costs a few cents in network fees and answers the question of whether the route is still open more reliably than any announcement.

Step 4: Put the date in the calendar

Enter December 1, 2026, and if you hold Noble balances, January 12, 2027 as well. The gap between announcement and shutdown is generous at just under three months; that is precisely why it tends to be forgotten.

Record keeping: why you should log every chain switch

A chain switch over CCTP looks like two events in your wallet's history: an outgoing entry on the source chain and an incoming one on the destination chain. Tax programs and portfolio tools do not always recognise the connection by themselves and then book the outgoing entry as a sale when in doubt. That is no statement about how such an event is to be treated for tax purposes; it is a purely practical warning: if you do not record the link yourself, you will barely be able to reconstruct it later.

So note the date, source chain, destination chain, amount and both event identifiers, ideally straight after the transfer. Filing it correctly right away saves you an unpleasant hour in the spring. How to keep such a record cleanly is shown by our overview of tax tools further down.

Phishing after the announcement: how to spot a fake migration page

In its announcement, Circle explicitly warned about fraud attempts riding on the switch. The pattern is the same with every shutdown and can be recognised by three features.

First: nobody working legitimately needs your recovery phrase in order to move a balance. A page that asks for it is finished the moment it asks. Second: real deadlines appear on the issuer's own site and can be read there; a deadline conveyed to you only by message and expiring in two hours is a pressure technique. Third: with a genuine migration the route always runs through tools you have used before. A new address that surfaces only in the wake of the announcement deserves suspicion.

What this survey does not show

Four limits belong with it explicitly. First, the figure of 103.6 million USDC on Noble is a snapshot of a single moment; it can move daily, and in the weeks until January it will quite probably do so markedly. Second, our count of the chain table says nothing about which wallet or which swap interface has already migrated in a given case; that can only be read off the respective application itself. Third, it remains open how the falling caps from October 31 work out concretely, because Circle has published no figures on that. Fourth, we did not establish the ownership structure of the Noble balance; whether it is predominantly private individuals or protocols cannot be read from the balance data alone.

For context from our own coverage: shutdowns of this kind are piling up at the moment. The Lisk chain ceases operations at the end of October, and there too a bridge deadline applies that falls before the actual final date. We worked the case through in a separate piece on the Lisk shutdown; the pattern of an early deadline and a final date is the same.

Timeline: from the announcement to the last redemption

• November 2025: Circle declares CCTP V2 the authoritative version; V1 becomes the legacy version with a transition window of around ten months.
• August 17, 2026: Coinbase stops deposits and withdrawals of USDC on Noble.
• September 10, 2026: Circle announces that it will discontinue USDC and CCTP on Noble entirely.
• October 13, 2026: no new USDC is minted on Noble through Circle Mint.
• October 31, 2026: the shutdown of CCTP V1 begins, the caps fall.
• December 1, 2026: the legacy version's contracts are halted.
• January 12, 2027: the Noble USDC contract and all transfer routes are halted, and a final snapshot is recorded.
• January 13, 2027: a manual redemption through customer support is to become possible for recorded balances.

Between today and the first effective date there are 32 days; until the legacy version comes to a standstill, 81. That is plenty of time, and precisely therein lies the risk: deadlines with a generous run-up are forgotten more reliably than those expiring tomorrow.

Primary sources for further reading

Circle lists the overview of supported chains together with domain identifiers in its developer documentation. The company describes the classification of the legacy version and the frame of the switch in its post on the CCTP versions. Both pages were reachable on September 11, 2026.

Checking the USDC bridge: what to take away

1. Look up which chain your USDC sits on. If it says Noble or Cosmos, you have until January 12, 2027, and the most convenient way out runs through a trading venue that still accepts Noble. Which providers come into question you can see in our overview of the best crypto exchanges.
2. Check the interface you use to change chain. If a switch there takes around a quarter of an hour, it is working with the standard transfer and should be tested again after December 1. If you are tidying up anyway while you are at it, the hardware wallet comparison helps with the question of where larger balances are better kept for the long run.
3. Record every chain switch in writing. Date, source chain, destination chain, amount and both event identifiers are enough. A tool that collects your events automatically takes the bulk of the work off you; we have set the common programs side by side in the overview of crypto tax tools.

(As of September 11, 2026. This article is not investment advice. Prices and fee structures change; check the terms with the provider before you buy.)