1 min read
Add as a preferred source on Google

Cosmos Hub Vote Would Move 566,067 Noble USDC to Injective

Proposal 1060 would route the community pool’s USDC.n through a four-of-six multisig. The vote is scheduled to close Nov. 3.

Mentioned assets
A silver token crosses a bridge beside four aligned metal keys / TokenPost.ai
A silver token crosses a bridge beside four aligned metal keys / TokenPost.ai

Cosmos Hub voters are considering a proposal to move 566,067.055810 USDC.n from the community pool to Injective, while Circle’s separate pause of Noble’s USDC contract and CCTP routes is scheduled for Jan. 12, 2027.

Proposal 1060 would send the pool’s full USDC.n balance to a four-of-six multisig. The group would use Skip:Go to convert the Noble-issued tokens to Injective-issued USDC, known as USDC.inj, and return them to the pool. The vote and transfer remained pending as of Nov. 2, with voting scheduled to close Nov. 3.

The proposal concerns one pool balance within a broader migration. As of Oct. 16, 12.70 million USDC had migrated to Injective, while 93.97 million USDC.n remained across the ecosystem, mostly on dYdX.

Circle’s CCTP V1 schedule calls for gradual burn-limit reductions beginning Oct. 31 and a general pause of V1 contracts on Dec. 1. It does not specify interim limit levels. Circle’s separate Noble schedule sets Jan. 12, 2027, for pausing the Noble USDC contract and CCTP routes to and from Noble.

After Dec. 1, exits from Noble may be limited to destinations that still support V1 burns. Circle has said, “Noble will not receive CCTP V2.” V2 uses separate contracts and APIs from V1. The broader CCTP V1 timeline sets a Dec. 1 pause date.

Voting on Proposal 1060 is scheduled to close Nov. 3.

Simon Yoon

Reporter

Simon Yoon reports on blockchain technology for TokenPost. Send corrections or tips to info@tokenpost.com.

Loading…