TLDR
Circle announced on September 10, 2026 that it will discontinue native USDC and CCTP V1 on Noble. New Circle Mint issuance to Noble stops October 13, CCTP V1 burn limits begin falling October 31, and routes may narrow after December 1. On January 12, 2027, Circle plans to pause the Noble USDC contract and every CCTP route to and from Noble. Self-custody holders can use an exchange deposit, a Noble DEX swap or a CCTP V1 exit before the pause, but each route carries a different network, liquidity and account-crediting check. Manual redemption starts afterward for qualifying snapshot balances; it is a controlled fallback, not a reason to wait.
Key takeaways
- Noble will not receive CCTP V2, according to Circle.
- Circle Mint stops minting new Noble USDC on October 13, 2026, while Mint redemptions remain available through January 12, 2027.
- CCTP V1 burn limits from Noble start reducing on October 31; after December 1, fewer destination chains may remain available.
- Circle says USDC remains transferable on Noble until the January 12 pause.
- An exchange that lists USDC does not necessarily accept deposits over Noble. Network and memo instructions must match.
- Post-pause manual redemption requires a holder-controlled wallet included in Circle's snapshot plus compliance and security checks.
- CryptoGuide Exchange is an independent research and comparison platform—not an exchange, broker, custodian, investment adviser or legal adviser.
What changed
Noble is a Cosmos appchain used for native asset issuance. Circle's documentation describes native USDC on Noble as movable to supported Cosmos appchains over IBC or to other CCTP domains through CCTP V1. That made Noble a routing hub, not merely another ticker on an exchange screen.
The retirement breaks that assumption in stages. Circle says it is concentrating on CCTP V2, which adds capabilities such as Fast Transfer and Hooks, but Noble will remain on the legacy version and will not be upgraded. The important user distinction is between a scheduled infrastructure shutdown and an immediate asset failure: Circle published an exit window and a later manual process, yet neither removes operational risk from delaying.
The Noble USDC timeline
| Date | What changes | User implication |
|---|---|---|
| Through Oct. 12, 2026 | Circle Mint Noble access, withdrawals, express routes and redemptions continue normally. | Verify and plan an exit while the widest set of routes remains. |
| Oct. 13, 2026 | New Circle Mint minting to Noble is disabled. | Do not interpret continuing transfers as continuing issuance support. |
| Oct. 31, 2026 | CCTP V1 burn limits begin reducing toward zero. | Large or time-sensitive exits may become harder even before shutdown. |
| After Dec. 1, 2026 | CCTP exits may be limited to chains that still accept V1 burns. | Recheck destination availability; an old route guide may be stale. |
| Jan. 12, 2027 | Noble USDC contract and all Noble CCTP routes are fully paused; Circle takes its balance snapshot. | Normal transfer-based exit methods end. |
| Jan. 13, 2027 | Circle's manual redemption process begins. | Eligibility, wallet control, snapshot inclusion and compliance checks apply. |
Who is affected
Exchange users
Users holding Noble USDC at a centralized exchange depend on that platform's migration and withdrawal policy. Users depositing self-custodied USDC depend on an explicitly supported Noble rail. A generic “USDC deposit” button is not enough: selecting Ethereum, Base or another network for a Noble transfer can cause loss or require manual recovery.
Self-custody and Cosmos users
USDC may be visible on a Cosmos appchain after moving there through IBC. Before acting, identify the token's origin and current chain, then verify the return route to Noble or another supported path in the wallet interface. Circle says its post-pause snapshot covers addresses on Noble, so users should not assume a balance represented on another appchain will automatically qualify.
CCTP integrators
Wallets, bridges and exchanges with Noble CCTP V1 integration need to remove the route before January 12. Circle warns that integrations relying on it will stop functioning after the pause. Users should therefore treat an app's route availability as time-sensitive, not as proof of ongoing issuer support.
Compare the exit routes
| Route | Verify first | Main risk |
|---|---|---|
| Deposit to a centralized exchange | The exchange names Noble as the USDC network; address, memo, minimum and maintenance status all match. | Wrong-network or missing-memo deposits may not credit automatically. |
| DEX swap on Noble | Exact output asset, pool liquidity, price impact, fees and the next withdrawal route. | Slippage or swapping into an asset with different issuer, bridge or liquidity risk. |
| CCTP V1 burn from Noble | Current destination support, burn limit, fees, finality and destination address. | Capacity and destination choices contract as the deadline approaches. |
| Manual redemption after pause | Official Circle Help Center instructions, wallet control, snapshot address and eligibility. | Compliance review, delays and phishing attempts around a non-standard process. |
Decision checklist before moving funds
- Confirm the asset is Circle-issued native USDC connected to Noble—not a similarly named bridged token.
- Identify the chain where the balance currently sits and whether IBC is part of the route.
- Open deposit instructions inside the receiving exchange; verify that “Noble” is explicitly listed.
- Copy the fresh address and memo, if required. Do not reuse saved instructions without checking.
- Check deposit minimums, credited confirmations, maintenance notices and whether withdrawals are open.
- For CCTP, check the live supported-domain page and available burn capacity.
- For a DEX, compare expected output with price impact and the cost of the next hop.
- Send a small test when the route and fee structure allow it.
- Save transaction hashes, IBC packet details and exchange deposit records.
- Finish before capacity tightens; do not plan around the final day.
Risk notes
A supported asset is not a supported network
Exchanges commonly list one USDC balance while accepting only selected deposit networks. Network choice is part of the transaction, not a cosmetic label. The recipient's current deposit page is the controlling instruction.
IBC adds another identity check
Cosmos wallets can display assets by symbol even when their denomination trace or origin differs. Verify the full token representation and route rather than relying on “USDC” alone. A transfer path that worked previously can also change as relayers, channels and applications update their Noble support.
Manual redemption creates a phishing theme
Circle says details will appear in its Help Center starting January 13, 2027 and specifically tells holders to use its blog and Help Center to avoid scams. Treat unsolicited “migration support,” search ads, direct messages and any request for a recovery phrase as hostile. A legitimate redemption process never needs your seed phrase.
CryptoGuide take
This is the kind of orderly wind-down that should still change user behavior early. The headline deadline is January 12, but the useful deadline is earlier: burn limits start falling October 31 and destination options may shrink after December 1. Exchanges earn trust here by naming the network unambiguously, publishing memo and cutoff rules, and telling users what happens to platform-held balances. Holders should choose a verified normal route while it is available rather than optimizing for the last possible exit.
FAQ
Is Noble USDC failing or depegging?
Circle's notice describes a planned discontinuation of chain and CCTP support, not a reported depeg. The operational risk is losing normal route access after the published deadlines.
Can I send Noble USDC to any exchange that lists USDC?
No. The exchange must explicitly accept USDC over Noble, and its address and memo instructions must be followed. Asset support and network support are separate.
What happens if I still hold Noble USDC after January 12?
Circle says it will snapshot remaining Noble balances and open a manual redemption process on January 13. Qualification requires a holder-controlled wallet in that snapshot plus Circle's compliance and security requirements.
Should I wait for Circle's shortlist of exit venues?
Circle says it will publish known venues but will not operate its own exit interface. If you already have a verified, suitable route, waiting can leave fewer CCTP options and less time to solve account or IBC issues.
Conclusion
Noble USDC holders have a defined migration window. Use it deliberately: identify the token and chain, verify the receiving rail inside the exchange or wallet, test the route, retain records and leave margin before the capacity reductions and final pause.
Related pages
- USDC route checks before CCTP V1 shutdown
- CCTP upfront fees: read the full USDC quote
- Circle Gateway Fast Deposit checks
- How to choose a crypto exchange
- Run a trust check