Ricerca verificata da fonti: Circle Noble USDC CCTP

Verified source facts

1. Circle says new USDC minting on Noble through Circle Mint will be disabled on October 13, 2026. 2. Circle says Noble redemptions through Circle Mint remain available until January 12, 2027, when Noble USDC and CCTP routes pause. 3. Circle says CCTP V1 burn limits begin reducing October 31, 2026 and a manual redemption process begins January 13, 2027 after a balance snapshot. 4. Circle's migration documentation says CCTP V2 is not deployed on Noble, so integrators cannot assume an in-place V2 route.

Comparison at a glance

1. Usage and measurement test: Mint cutoff

Stablecoin adoption cannot be inferred from a single gross counter. The mint cutoff dimension concerns October 13 new issuance stop. Define the economic job, unit of observation, time window and entities included before counting, then remove new-mint assumptions. Otherwise one routed transaction, exchange rebalance or contract hop may be mistaken for several independent users or payments.

Separate ledger events from economic outcomes. A transfer can be real on-chain yet still represent internal treasury movement, automated arbitrage, bridge routing, collateral management or redemption rather than a purchase. Official sources can frame the categories, but they do not resolve account processing time. The dataset and classification method therefore belong beside every headline number.

For mint cutoff, publish the numerator, denominator and exclusions that support the claim. Make the analyst remove new-mint assumptions, and compare at least one activity metric with one outcome metric relevant to October 13 new issuance stop. Because account processing time remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.

2. Usage and measurement test: Transferability

The transferability dimension concerns Noble transfers before final pause. Define the economic job, unit of observation, time window and entities included before counting, then verify destination support.

Official sources can frame the categories, but they do not resolve venue liquidity.

For transferability, publish the numerator, denominator and exclusions that support the claim. Make the analyst verify destination support, and compare at least one activity metric with one outcome metric relevant to Noble transfers before final pause. Because venue liquidity remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.

3. Usage and measurement test: CEX exit

The cex exit dimension concerns exchange accepting Noble USDC. Define the economic job, unit of observation, time window and entities included before counting, then test deposit route.

Official sources can frame the categories, but they do not resolve future exchange support.

For cex exit, publish the numerator, denominator and exclusions that support the claim. Make the analyst test deposit route, and compare at least one activity metric with one outcome metric relevant to exchange accepting Noble USDC. Because future exchange support remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.

4. Usage and measurement test: DEX exit

The dex exit dimension concerns swap liquidity on Noble. Define the economic job, unit of observation, time window and entities included before counting, then measure slippage and contract identity.

Official sources can frame the categories, but they do not resolve future depth.

For dex exit, publish the numerator, denominator and exclusions that support the claim. Make the analyst measure slippage and contract identity, and compare at least one activity metric with one outcome metric relevant to swap liquidity on Noble. Because future depth remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.

5. Usage and measurement test: CCTP burn

The cctp burn dimension concerns declining V1 limits. Define the economic job, unit of observation, time window and entities included before counting, then migrate before constraints tighten.

Official sources can frame the categories, but they do not resolve daily available capacity.

For cctp burn, publish the numerator, denominator and exclusions that support the claim. Make the analyst migrate before constraints tighten, and compare at least one activity metric with one outcome metric relevant to declining V1 limits. Because daily available capacity remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.

6. Usage and measurement test: Destination chain

The destination chain dimension concerns remaining V1-supported route. Define the economic job, unit of observation, time window and entities included before counting, then verify current domain status.

Official sources can frame the categories, but they do not resolve later deprecation.

For destination chain, publish the numerator, denominator and exclusions that support the claim. Make the analyst verify current domain status, and compare at least one activity metric with one outcome metric relevant to remaining V1-supported route. Because later deprecation remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.

7. Usage and measurement test: Final pause

The final pause dimension concerns January 12 route closure. Define the economic job, unit of observation, time window and entities included before counting, then complete automated exits early.

Official sources can frame the categories, but they do not resolve operational extension.

For final pause, publish the numerator, denominator and exclusions that support the claim. Make the analyst complete automated exits early, and compare at least one activity metric with one outcome metric relevant to January 12 route closure. Because operational extension remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.

8. Usage and measurement test: Snapshot

The snapshot dimension concerns eligible holder-controlled balance. Define the economic job, unit of observation, time window and entities included before counting, then retain address evidence.

Official sources can frame the categories, but they do not resolve snapshot discrepancy.

For snapshot, publish the numerator, denominator and exclusions that support the claim. Make the analyst retain address evidence, and compare at least one activity metric with one outcome metric relevant to eligible holder-controlled balance. Because snapshot discrepancy remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.

9. Usage and measurement test: Manual redemption

The manual redemption dimension concerns compliance-gated process from January 13. Define the economic job, unit of observation, time window and entities included before counting, then prepare non-secret records.

Official sources can frame the categories, but they do not resolve processing duration.

For manual redemption, publish the numerator, denominator and exclusions that support the claim. Make the analyst prepare non-secret records, and compare at least one activity metric with one outcome metric relevant to compliance-gated process from January 13. Because processing duration remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.

10. Usage and measurement test: Integrator change

The integrator change dimension concerns remove Noble V1 route. Define the economic job, unit of observation, time window and entities included before counting, then deploy and test fail-closed behavior.

Official sources can frame the categories, but they do not resolve dependent application readiness.

For integrator change, publish the numerator, denominator and exclusions that support the claim. Make the analyst deploy and test fail-closed behavior, and compare at least one activity metric with one outcome metric relevant to remove Noble V1 route. Because dependent application readiness remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.

Decision scenarios

Scenario 1: when mint cutoff becomes decisive

Consider a reader whose main constraint is October 13 new issuance stop. The correct response is not to infer a universal platform or product winner. It is to remove new-mint assumptions, retain the evidence, and define a stop condition before funds or permissions are committed. If the evidence changes, the decision must be reopened. This produces a repeatable operating rule rather than a one-time opinion.

Scenario 2: when transferability becomes decisive

Consider a reader whose main constraint is Noble transfers before final pause. It is to verify destination support, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when cex exit becomes decisive

Consider a reader whose main constraint is exchange accepting Noble USDC. It is to test deposit route, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when dex exit becomes decisive

Consider a reader whose main constraint is swap liquidity on Noble. It is to measure slippage and contract identity, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when cctp burn becomes decisive

Consider a reader whose main constraint is declining V1 limits. It is to migrate before constraints tighten, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when destination chain becomes decisive

Consider a reader whose main constraint is remaining V1-supported route. It is to verify current domain status, retain the evidence, and define a stop condition before funds or permissions are committed.

Sources and editorial method

• Circle is discontinuing support for USDC and CCTP V1 on Noble — Circle
• Migrate from CCTP V1 to V2 — Circle Developer Docs
• CCTP Noble Cosmos Module V1 — Circle Developer Docs