Circle CCTP V1 Deprecation News August 28, 2026: When Legacy USDC Transfers Stop
Circle will reduce CCTP V1 burn limits from October 31 and pause legacy contracts on December 1. Here is what wallets, bridges, and users need to check.
Circle set the final dates for legacy CCTP transfers
Circle announced on August 27, 2026, that Cross-Chain Transfer Protocol V1 will begin its final wind-down on October 31 and its legacy contracts will be paused on December 1, 2026. Apps that still send USDC through V1 must migrate to CCTP V2, now called CCTP, before that pause.
The first deadline is not a clean switch. Circle plans to reduce V1 burn limits from October 31, gradually lowering performance and new transfer capacity over one month. On December 1, integrations still pointing to V1 contracts will stop initiating cross-chain USDC transfers.
This is a developer and infrastructure deadline, not a change to USDC balances generally. Circle says pending redemptions will remain processable during the phase-out, but users should not assume that every wallet, bridge, exchange, or payment app will migrate on time.
1. October 31 starts a controlled reduction in new V1 burns
CCTP moves native USDC between supported blockchains through a burn-and-mint process. A V1 transfer burns USDC on the source chain, waits for Circle's attestation after the required finality, and then mints the corresponding amount on the destination chain.
Circle's retirement plan targets the first stage. From October 31, V1 message and burn limits will tighten until no new burns can begin. That is intended to bring V1 volume toward zero before the contracts are paused.
For users, a late migration may first appear as reduced route availability, longer waits, lower limits, or an app disabling a particular transfer path. The exact experience belongs to the app or bridge providing the route. Circle did not announce one universal consumer interface or recovery process for every third-party integration.
2. December 1 is the hard stop for legacy integrations
Circle says V1 contracts will be paused on December 1. An integration that still calls legacy contract addresses or V1 APIs will not keep working merely because the same source and destination chains are supported by V2.
The versions are not backward compatible. Migration requires changes across the transfer path, including:
- new contract addresses and interfaces
- updated contract calls and parameters
- V2 API endpoints instead of the legacy V1 endpoints
- new message and attestation response handling
- an explicit choice between Standard and Fast Transfer where available
- fee handling for Fast Transfer and supported fee routes
Updating only a button label or API base URL is not sufficient. A production migration must also cover transaction monitoring, duplicate protection, timeout behavior, failed attestations, destination-chain submission, and support procedures for transfers already in progress.
3. Circle says pending redemptions will remain available
The phase-out does not mean pending V1 transfers are automatically lost on October 31 or December 1. Circle's migration guide says it will keep minter allowances above the total pending attestations so existing redemptions can be processed before V1 contracts are fully paused.
That assurance has a precise boundary. It addresses pending CCTP redemption capacity; it does not guarantee that a third-party app will display the transfer correctly, continue polling the right endpoint, submit the destination-chain transaction, or provide timely support.
Before using a route near the deadline, users should check whether the provider explicitly supports CCTP V2 and whether its status page identifies the source chain, destination chain, expected time, fee, and transaction references. A generic claim that an app supports USDC is not proof that its cross-chain route has migrated.
4. V2 changes both contract calls and attestation retrieval
V1 applications commonly extract a message from the source-chain transaction, hash it, and request the attestation through a V1 endpoint. Circle's V2 workflow can return the message, attestation, and decoded data from a single messages endpoint using the source domain and transaction hash.
The smart-contract interface also changed. Circle documents new V2 addresses and additional parameters for the main burn function, including the destination caller, maximum fee, and minimum finality threshold. V2 adds a hook-enabled burn function and has no equivalent for the removed V1 replacement function.
These differences matter during recovery. Teams need to test more than successful transfers. They should verify an expired or delayed attestation, a fee above the user's limit, an unsupported route, a wrong destination, a restarted worker, and a duplicate callback without burning or minting twice.
5. Fast Transfer is optional and can carry a variable fee
CCTP V2 supports Standard Transfer and, on eligible source chains, Fast Transfer. Standard Transfer waits for the source chain's required finality. Fast Transfer can make funds available sooner by using Circle's fast-transfer allowance and charges a variable fee based on the source chain.
Faster does not mean universally available. Circle's current chain table marks Fast Transfer only where it provides a useful speed improvement, and feature support differs by route. Apps should fetch or calculate the applicable fee before the user commits and must not silently switch transfer speed or exceed an approved maximum.
Users should compare the full route rather than the headline speed: source and destination support, quoted fee, finality assumptions, wallet approval, and the provider's handling of a transfer that cannot complete immediately.
6. Chain support must be checked at the asset and route level
Circle said CCTP V2 supports 27 blockchains in its August 27 announcement. Its documentation also shows that capabilities are not identical across all chains. Standard Transfer, Fast Transfer, upfront fees, and forwarding support vary.
Token support varies too. USDC is available across most current CCTP domains, while Circle's table lists BNB Smart Chain for USYC rather than USDC. Noble and Sui remain identified in the documentation as V1-only at the time of review, although Circle says Sui is expected to gain V2 support before the phase-out begins.
That makes a network name alone insufficient. A provider must validate the token, source chain, destination chain, contract version, transfer mode, and current capability before accepting a transfer.
What happened on the key dates
| Event | Exact date | What it means |
|---|---|---|
| Circle announced the V2 transition | November 14, 2025 | Developers received advance notice that V1 would be retired |
| Circle published the final wind-down reminder | August 27, 2026 | The October 31 and December 1 operational deadlines were confirmed |
| V1 burn limits begin declining | October 31, 2026 | New legacy transfer capacity and performance will be reduced over one month |
| V1 contracts are scheduled to pause | December 1, 2026 | Integrations still using legacy contracts stop transferring USDC cross-chain |
What users and integration teams should verify
- the app or bridge explicitly names CCTP V2 support
- every active source-to-destination route uses reviewed V2 contract addresses
- the application uses the V2 message and attestation workflow
- fees and transfer speed are shown before approval
- pending V1 transfers remain visible and recoverable through the transition
- duplicate submissions cannot create a second burn or destination action
- monitoring distinguishes source burn, attestation, destination mint, and final receipt
- support documentation explains what to do when one stage is delayed
Circle has supplied a dated retirement schedule, but migration proof belongs to each integration. A wallet or bridge is ready only after its real routes, failure recovery, and pending-transfer handling work on V2; a roadmap statement is not enough.
Frequently asked questions
Q: Will CCTP V1 stop working on October 31, 2026?
A: The wind-down begins then. Circle plans to reduce V1 burn limits and performance over the following month. The legacy contracts are scheduled to pause on December 1.
Q: Will pending V1 transfers disappear?
A: Circle says pending redemptions will remain available and that minter allowances will cover pending attestations during the phase-out. Users still depend on their app or bridge to complete and display the remaining steps correctly.
Q: Can an app migrate by changing only its API URL?
A: No. V2 uses different contract addresses, interfaces, function parameters, endpoints, response handling, and transfer-speed controls.
Q: Is Fast Transfer required?
A: No. V2 supports Standard Transfer, while Fast Transfer is available only on eligible source chains and can include a variable fee.
Q: Does the deadline affect all USDC holdings?
A: No. It applies to cross-chain transfers routed through CCTP V1. Holding or transferring USDC on one chain is a separate activity.
Q: How can a user tell whether a route is ready?
A: Check for an explicit CCTP V2 statement from the provider, current route availability, a fee and speed quote, transaction-stage tracking, and documented recovery for pending transfers.
Sources
- Circle: CCTP V1 deprecation announcement, published August 27, 2026
- Circle Developers: CCTP V1-to-V2 migration guide, accessed August 28, 2026
- Circle Developers: supported blockchains and domains, accessed August 28, 2026
- Circle Developers: CCTP V1 architecture and transfer flow, accessed August 28, 2026
Cross-chain transfers involve smart-contract, network, wallet, operational, and irreversible-address risks. This article is not investment advice. Create your free KrptoPay wallet to manage supported assets and follow source-backed crypto developments.