This is the fourteenth of Hub Weekly Thursday recaps, straight from the Hub Unit team, per the cadence we committed to in the From Chaos to Stability to Growth post.
Every Thursday, we will call out significant Cosmos Hub updates on the forum, with a short companion thread on X, recapping announcements, live events like validator or community calls, and ecosystem updates!
For more info, see the linked posts, and contact @RoboMcGobo on telegram to submit news for the weekly.
This week: the CCTP (Legacy) deprecation, the Gaia v28 vote, Hydro’s migration, and Stargaze analytics.
-
CCTP (Legacy) Deprecation: Circle announced the deprecation of legacy CCTP, and our full article covers what it means for Cosmos: Noble USDC keeps working, and the migration stays on track
-
Gaia v28: the ICS removal upgrade is on-chain as Proposal 1052, and voting is live
-
Hydro: the migration to the Hub is complete, following the v27.0.0 upgrade
-
Stargaze: analytics is live, with Cosmos Hub data integrated throughout
CCTP (Legacy) Deprecation: Noble USDC Keeps Working, and the Migration Stays on Track
Circle announced the deprecation of legacy CCTP this week. We published a full article on what the announcement means for the Cosmos ecosystem, which you can read on X. This section is the summary, and it also serves as this week’s USDC status update.
The short version: this announcement does not impact the ecosystem’s migration from Noble USDC to Injective USDC, and CCTP transfers from Noble will continue to be supported following the legacy CCTP deprecation. The migration remains on track, with an anticipated start in mid-September. Cosmos Labs has been coordinating closely with Circle, Injective, and the ecosystem’s largest USDC users, including dYdX and Osmosis, ahead of this announcement.
The deprecation: what did Circle actually announce?
Circle is deprecating the legacy CCTP protocol version beginning October 31, 2026, with burn limits stepping down over the following weeks until they reach zero on December 1.
What the announcement does not do is set a schedule for when support for USDC on Noble will end. If you hold Noble USDC, nothing changes for you today: Noble USDC continues to work as it does now, Noble will continue to be supported by CCTP beyond the legacy deprecation timeline, and Circle will publish any Noble-specific transition timelines separately. Any termination of Noble USDC support will be executed with sufficient time to allow for a full migration of the ecosystem’s USDC to Injective.
The rollout: what is live now, and what comes next?
-
Live today: Injective USDC on Skip:Go mainnet, over CCTP. Skip:Go now routes Injective USDC (USDC.inj) on mainnet, with these destinations live: dYdX, Osmosis, Cosmos Hub, Terra 2.0, Neutron, and Zigchain. This is a developer-focused, manual migration flow: each bridging step is initiated manually, with gas paid on each network. It is built for teams, protocols, and experienced liquidity providers to set up pools and markets for USDC.inj, test routes and integrations, and begin moving protocol, treasury, and market-maker liquidity. Most community members should not migrate using this method. The migration guide covers the manual path.
-
Mid-September: full migration support for the community. The dedicated migration flow launches on Skip:Go in mid-September, with transaction forwarding and cross-chain gas handled automatically. This will be the best path for the community to migrate. A migration API for wallets and frontends goes live shortly after, so teams can embed migration natively in their own products.
Last week’s issue named an earlier working target for the dedicated flow. Mid-September is the current target, and as with every stage of this rollout, we will confirm each piece publicly once it is live.
What this means for you
-
If you hold USDC in Cosmos: No action is needed today. Keep following @cosmoshub, @circle, @injective, and @dydx on X for the latest migration timelines and tooling.
-
If you’re a chain, infra provider, or developer integrating Noble USDC: Begin setting up liquidity pools and local markets for Injective USDC now. Review the migration guide for how to move USDC from Noble to Injective. You will have access to a migration API with automatic gas handling when the full migration flow goes live in mid-September.
-
If your chain is not yet supported on Skip:Go: Chains that want to be supported USDC.inj destinations need IBC relayers to Injective. If your chain isn’t relayed yet, establish an IBC connection to Injective and then reach out to us on Discord to be added to Skip:Go.
Gaia v28: The ICS Removal Upgrade Is On-Chain as Proposal 1052, and Voting Is Live
The Gaia v28 testing process, which covered a full unbonding period on the public testnet, has wrapped, and the mainnet software upgrade proposal is now on-chain: Proposal 1052, Gaia v28.0.0. Voting is live.
As covered in the advance notice thread, v28 removes the ICS provider module from the Hub. The proposal specifies the upgrade height, and the upgrade is state-breaking and mandatory once the vote passes, so validators should prepare to update their binaries at the specified height.
Validators: cast your vote. Upgrade notices go out through the usual channels. Questions and feedback remain welcome on the advance notice thread.
Hydro: The Migration to the Hub Is Complete
Hydro, the liquidity allocation and auction platform built by Informal Systems, has completed its migration to the Cosmos Hub, following the v27.0.0 upgrade. The Hydro team shared the details in their announcement.
For anyone newer to it: Hydro is where ATOM stakers direct protocol-owned liquidity. Stakers lock their staked ATOM in exchange for voting power, with longer lockups carrying more weight, and projects bid in monthly rounds for liquidity deployments funded from the community pool. Until now, Hydro’s contracts ran on Neutron; with this migration, the platform runs natively on the chain it allocates for.
What the move means in practice:
-
Locking, voting, and auction rounds now happen directly on the Hub. ATOM stakers interact with Hydro on the same chain their stake lives on.
-
The v27.0.0 upgrade did the enabling work, bringing what Hydro needed to run natively on the Hub.
-
For existing participants: the Hydro team’s announcement and hydro.markets cover what, if anything, changes for current lockups and votes.
Stargaze Analytics: Marketplace Data Across Stargaze and the Cosmos Hub, Live Now
Stargaze shipped its analytics page this week (announcement), and Cosmos Hub data is integrated throughout. What’s live:
-
Marketplace analytics. Volume, sales, mints, holders, and creator earnings, with timeframes from one day to all time, and a toggle between Stargaze Chain, the Cosmos Hub, or both.
-
Per-collection analytics. Every collection has an Analytics tab with floor price, sales, and listing depth.
-
Profile analytics. Your own profile has one too: portfolio value, realized PnL, win rate, and top collections by volume.
-
Historical data. Token history spans both the Stargaze chain era and the Cosmos Hub era.
That’s all for this week - thanks to everyone engaging across the forum, validator channels, and Telegram. Looking forward to next week’s update! Please let us know if you like the Weekly format, and what else you’d like to hear from us.
-
Join the biweekly validator calls
-
Join the next community call: Register for the community calendar here