Wednesday, September 16, 2026

Creating liberating content

CoinEx quits after 9...

Crypto exchange CoinEx is shutting down after nine years, citing shrinking revenue and...

Bitcoin, BTC-Related Stocks Tumble...

Bitcoin’s price tumbled — along with crypto-related stocks — following the blockage of...

Bitcoin Core v32 RC1:...

Bitcoin Core v32.0rc1 has turned the Sept. 14–Oct. 10 window into a concentrated...

AI Could Be Bitcoin’s...

Artificial intelligence may turn out to be an unexpected driver of...

Circle sets Oct. 31 burn cuts

Circle’s CCTP V1 deprecation gives developers still using the first version of its Cross-Chain Transfer Protocol (CCTP) 95 days to migrate before the legacy contracts stop processing USDC transfers.

The company said CCTP V1 burn limits will begin falling on Oct. 31. A burn limit caps how much USDC can be destroyed on one chain for reminting on another. Circle plans to reduce those limits and transfer capacity through November, then pause the contracts on Dec. 1. Any integration still pointing to V1 at that point will no longer move USDC across chains.

The cutoff governs cross-chain routing. Circle’s migration guide says users will retain access to funds during the phase-out and pending redemptions will remain available. An attestation is Circle’s signed approval for USDC burned on a source chain to be minted on a destination chain. Circle said it will keep enough minting capacity available to complete outstanding attestations before V1 is fully paused.

Read More:  Forget ETF flows, Bitcoin's real threat is a hidden $39,900 liquidation wall

Related Reading

Circle still tells users to buy Noble USDC on Coinbase after cutoff date passes

CCTP V1 deprecation: code changes and exposed routes

The migration requires code changes. CCTP V2, now branded simply as CCTP, uses different contract addresses, interfaces and APIs and is incompatible with V1.

Integrators must point to the V2 versions of TokenMessenger, MessageTransmitter and TokenMinter, update their contract interfaces, and change calls to depositForBurn. The V2 function adds parameters for the permitted destination caller, maximum fee and minimum finality threshold. Developers must also replace legacy attestation calls with the /v2/messages/{sourceDomainId} flow, choose standard or fast settlement where available, and handle applicable fees.