Burn limits on Circle's legacy USDC bridge began falling on October 31, and the V1 contracts pause on December 1. On the same migration page, a block of instructions written for AI coding assistants still says Noble, Sui and Aptos "still require V1." Circle's own release notes say two of those three chains moved to V2 weeks ago. Circle's legacy cross-chain transfer protocol entered its final month today. From October 31, burn limits on CCTP V1 start falling toward zero, and on December 1 the V1 contracts pause. Any app still using them will stop moving USDC between chains. Most coverage has focused on those two dates. But the guide developers are told to follow, Circle's V1-to-V2 migration page , contains a mistake in the section written for AI tools. Embedded in the page is an "Agent Instructions" block, guidance meant for AI coding assistants that read the documentation for developers. It says: "Noble, Sui, and Aptos still require V1." For two of those three chains, Circle's other published records say the opposite. What Starts On October 31 The schedule is fixed. Circle announced in an August 27 blog post that "CCTP V1 (Legacy) deprecation begins October 31, 2026 and completes on December 1, 2026." From today, V1 burn limits fall, and the migration guide says "message limits will tighten over time until no new burns can be initiated." On December 1 the V1 contracts pause, and any integration still pointing at them can no longer transfer USDC between chains. Circle has been firm about this. "Migration from CCTP V1 (Legacy) to CCTP V2 is required, not just recommended," the company wrote, adding that V2 "uses separate contracts and APIs and is not backward compatible." Funds already in transit are protected. The guide says "all pending redemptions will remain available" during the phase-out, and that Circle "will maintain minter allowances greater than the total of pending attestations." The Line Hidden In Circle's Agent Instructions The migration page has two audiences. Human readers see the main guide. AI coding assistants also parse a separate instruction block, which tells them how to answer developer questions. In that block, the guidance is clear: "Noble, Sui, and Aptos still require V1." The main text above it says something different. According to the human-facing guide, "CCTP V2 contracts are available on all CCTP V1 chains except for Noble and Sui," and "Sui will be supported by V2 before the deprecation begins." Aptos isn't listed as an exception there at all. So one page gives two different answers about the same chains, and the out-of-date answer is the one written for AI tools. What Circle's Own Records Say About Sui And Aptos Circle's 2026 CCTP release notes show how out of date the instruction is: August 25: "CCTP V2 support for Aptos added (domain 9)." The note says Aptos had previously been available only on CCTP V1 (Legacy). October 8: Sui mainnet and testnet were added as supported CCTP chains (domain 8). The migration guide had said this would happen before deprecation began. Circle's supported chains and domains page now lists both Sui and Aptos in its CCTP table, with Standard Transfer support. The page's V1-only section names one chain: Noble. As of today, Aptos has had V2 for more than two months and Sui for more than three weeks. The instruction telling AI tools that both "still require V1" was overtaken by Circle's own updates before the shutdown began. Noble Is The Real V1-Only Chain Noble is the one chain in that line where the instruction is still accurate, and it is leaving CCTP entirely. In a September 10 announcement , Circle said "Noble will not receive CCTP V2" and set out its exit: October 13: new USDC minting to Noble through Circle Mint stopped. October 31: CCTP V1 burn limits began falling. December 1: CCTP exits from Noble may be limited to destination chains that still support CCTP V1. January 12, 2027: the Noble USDC contract and CCTP routes are fully paused, and Circle takes a snapshot of remaining balances. January 13, 2027: Noble is no longer reachable through Circle Mint or CCTP, and a manual redemption process opens. For Noble, V1 is the only route available, and it is being closed. Why A Stale Instruction Matters Now A wrong line in documentation would normally be a small issue, but the timing makes this one more serious. Many developers now ask AI assistants to write or update integration code, and those assistants read documentation like this page. A developer asking how to bridge USDC to Sui or Aptos could be told, based on Circle's own instruction block, to use V1. That is the route whose burn limits started falling today and which pauses in a month. The fix in the code is not small either. Moving to V2 means: pointing at new contract addresses using new ABIs, since depositForBurn takes extra parameters choosing a transfer speed through finalityThreshold replacing the attestation flow with /v2/messages/{sourceDomainId} accounting for fees, which V1 did not charge An integration built on V1 now would have to be rebuilt within weeks. What Integrators Should Check Before December 1 For teams working with Sui and Aptos, the published records point one way: build on V2, using the contract addresses for domains 8 and 9. Don't follow the V1 guidance from the agent-instruction block. For Noble, the deadline is January 12, 2027. Before then, integrators need to remove Noble as a CCTP route, and holders need to move or redeem their USDC. For everyone else, the burn-limit reductions have started. December 1 is the last day V1 integrations work, and any app still on V1 after that will stop moving USDC between chains. Disclosure: This is not trading or investment advice. Always do your research before buying any cryptocurrency or investing in any services. Follow us on X @nulltxnews
