New Noble USDC issuance through Circle Mint stopped on October 13, 2026; that cutoff did not itself stop ordinary Noble USDC transfers. For a holder checking a balance on October 27, the first useful question is where that balance actually sits. A wallet labelled Cosmos, a deposit recorded by an exchange and USDC held directly on Noble require different checks before moving anything.
Read the cutoff as an issuer-service change
Circle’s September reserve report, released in October, records Noble as redemption-only from October 13 in its blockchain definitions. See the original reserve report. The wording matters: stopping issuance through Circle Mint does not mean every existing token has disappeared or every balance screen is wrong. It also does not give every wallet owner an institutional Circle Mint account.
The Noble-specific notice schedules the USDC contract and CCTP pause for January 12, 2027, followed by manual redemptions from January 13. Those are later stages, not events already completed in October. A future redemption procedure is also not a reason to assume that a route visible in an old wallet will remain usable until the last day.
Follow the balance, not just the ticker
Circle’s Noble module documentation describes native issuance on Noble and movement to other Cosmos appchains through IBC. Consequently, a USDC label in a Cosmos wallet is not enough to establish the chain holding the asset or its representation. Record the actual chain, asset identifier and service custody before selecting a destination. An exchange’s internal USDC balance is another distinct record: ask about its supported deposit and withdrawal networks rather than treating its account label as a Noble address.
| Where your record is | Evidence to collect | Decision before sending |
|---|---|---|
| Self-custody balance directly on Noble | Noble account, asset identifier, balance and transaction history | Does the chosen recipient currently accept that exact network and asset? |
| USDC representation on another IBC-connected chain | Current chain and denomination trace, plus the app’s supported route | Does the route handle this representation, or require another supported step? |
| Custodial exchange or application balance | Account statement and available network options | Can the service credit or withdraw the balance through the intended network now? |
| A withdrawal already submitted | Withdrawal record and any published chain transaction | Is there an unfinished service operation, rather than another transfer to initiate? |
This worksheet is a method for separating cases, not a list of venues that have been tested. A receiving service’s current deposit instructions should resolve ambiguity. Never substitute a familiar address format for confirmation of network support. A small test, where permitted and above the service’s minimum, tests that one path at that time; it does not reserve capacity for a later transaction.
An available exit today is narrower than a final deadline
Noble remains listed as legacy-only in Circle’s current CCTP domain documentation. Circle’s Noble notice warns that legacy burn capacity starts declining on October 31 and destinations may narrow after December 1. It does not promise a particular venue’s liquidity or your account’s access. A displayed quote should therefore be assessed alongside the supported route, expiry, charges and recipient conditions.
- Locate the balance using the worksheet before choosing a migration or swap screen.
- Open the recipient’s current network instructions and confirm the exact asset, minimum and account requirements.
- Check the route’s present availability and the destination’s crediting conditions; preserve that evidence with the quote.
- After submitting, reconcile the original balance, destination receipt and any custodial credit. Investigate a missing stage before creating another transfer.
For an illustrative case, suppose a wallet shows an IBC-held asset while an exchange offers only a different USDC deposit network. The shared ticker does not establish a valid direct deposit. The missing work is proving a supported route between those records. It is not solved by sending to the exchange address and hoping the receiving service converts the asset.
Keep a manual-redemption claim separate from an ordinary swap
Circle makes its later manual process conditional on wallet control, inclusion in the pause-day snapshot, and compliance and security checks. Do not treat that notice as unconditional reimbursement or follow a portal supplied by a direct-message account. Preserve your own records; use the issuer’s published support channels for the actual procedure.
If comparing a no-account swap with another route, begin with supported coins and networks, then read how an exchange order works. Open simple swap only for a pair and network actually offered; these links do not assert that KOT.CASH accepts Noble USDC. Its AML policy remains relevant to an eligible order. Finishing a token transfer and satisfying a recipient’s crediting rules are separate checks.
FAQ
Does USDC on the Noble network stop moving when Circle Mint issuance ends?
The Noble notice explicitly separates the October issuance cutoff from the later pause. Establish the current network and recipient support before interpreting a visible balance as either frozen or ready for any deposit.
Does a USDC Noble bridge label prove that an exit still works?
A label is not evidence of a currently supported source and destination. Verify the application’s actual route and the receiving service’s conditions before authorizing a transfer.
Can I send USDC from Noble to Solana by reusing a deposit address?
A destination address alone does not move an asset between chains. You need a supported route that delivers the correct asset on the recipient’s network; this article does not certify a live venue.
Related on KOT.CASH
Sources
- www.circle.com/blog/circle-is-discontinuing-support-for-usdc-and-cctp-v1-on-noble
- developers.circle.com/cctp/v1/noble-cosmos-module
- developers.circle.com/cctp/concepts/supported-chains-and-domains
- 6778953.fs1.hubspotusercontent-na1.net/hubfs/6778953/USDCAttestationReports/2026/2026%20USDC_Examination%20Report%20September%2026.pdf