Hub Weekly Update #13: August 21, 2026
hub-weekly-13-landscape 1500×600 300 KB This is the thirteenth of Hub Weekly recaps, straight from the Hub Unit team, per the cadence we committed to in the From Chaos to Stability to Growth post. Every week, 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: Injective USDC on Skip Go mainnet, tokenomics Phase 2, Gaia v28 testing, and the August validator call. • Injective USDC : A developer-focused bridging flow is live on Skip Go, letting teams set up pools, start testing, and prepare for migration • ATOM tokenomics : Phase 2 mechanism evaluation is underway with Gauntlet, with community-proposed designs in the initial evaluation set • ICS deprecation : the Gaia v28 testing process is in its final stretch, with the mainnet proposal to follow • Validator call : the August 12 recap covers validator set health, governance quorum, and the tooling survey results Injective USDC: A Developer-Focused…
Excerpt (1196 of 9818 characters). Read the whole post on the forum ↗
Absolutely thrilling to read!!! Thanks @RoboMcGobo!!
Good to know that regular users do not need to take any action yet. When the user migration flow is ready, will there be a simple announcement or guide that wallets can share with users so they know which USDC they hold and what they need to do?
Clear communication will be important to avoid confusion, especially for multichain wallets such as Gem Wallet.
Yep we’ll have migration guides!
Hey Everyone,
I’m trying to find Snapshots for cosmoshub-4 chain that are a few months old.
My purpose is to use that snapshot and do a Archive (prune=nothing) sync from that point onwards to save Archive data for that time.
If anyone can help me, or atleast point me to any resource, it would be a big help.
Thankyou.
First of all, a sincere thank you to the Hub team and Gauntlet for the immense dedication, research, and technical effort behind this update and the Phase 2 modeling. How will all of this be implemented in practice? I would like to raise a few key considerations early in the design phase—precisely so all this valuable work and analysis isn’t rejected at the governance voting stage, forcing everyone back to square one if retail delegators feel unfairly penalized: 1. Duration-based Staking: Hard-locking ATOM for 6 to 12 months for a slight APR boost is simply not attractive given the inherent volatility of the crypto market. Other ecosystems handle loyalty incentives dynamically (for instance, scaling APR retroactively based on uninterrupted holding time, without stripping away emergency liquidity). Enforcing an inflexible lock where funds cannot be unstaked under any circumstance is far too rigid; the downside risk during market drawdowns heavily outweighs the extra yield. 2. Empty Block Throttling (Cutting Emissions): This mechanic directly penalizes delegators. If emissions are throttled during low-activity periods, our rewards drop while we still shoulder the exact same…
Excerpt (1196 of 2261 characters). Read the whole post on the forum ↗
The wallet experience point is interesting. For an average delegator, what information would help most when considering validators outside the top group—clearer descriptions, commission and performance details, or something else?
Making that choice easier without overwhelming users would be valuable.