Cosmos Hub Validator Call: Recap

Q3 delegations, Gaia v27.6.0 and v28.0.0, the USDC migration to Injective, validator set health, and validator tooling The following is a recap of the August 12, 2026 Cosmos Hub validator call. These calls occur once per month, and recaps like this one are posted on the Cosmos Hub forums following each call. This month’s call covered ecosystem updates, validator set health, governance participation, and results from the validator tooling survey. Delegation program: Q3 update The Q3 delegation review is nearing completion. A revised update will be published once the final count is confirmed. The team is also evaluating whether future reviews should place greater weight on recent participation. Any proposed methodology change will be shared for feedback before adoption. Gaia v27.6.0: larger CosmWasm contracts on the Hub Gaia v27.6.0 went live on mainnet on August 5 after proposal 1049 passed on August 4. The upgrade doubled the CosmWasm contract-size limit and enabled governance-proposal and validator-staking gRPC queries, expanding what developers can deploy and read on the Hub. Gaia v28.0.0: the ICS module comes out A second upgrade went to testnet on August…

Excerpt (1198 of 5538 characters). Read the whole post on the forum ↗

Picking up on the validator tooling section — we would like to put our hand up for upgrade notifications . Some context on why us rather than someone else: we already run a version of this for ourselves. VoidStake operates a monitoring stack for our own Hub validator — scheduled workers polling chain state, node health checks, and alerting on validator state with email and Telegram delivery. Adding a configurable notification layer is an extension of something already in production, not a greenfield build. ( our validator profile , for context on who we are.) What we could operate: • Configurable upgrade notifications , with email as a first-class delivery channel alongside webhooks. Email was raised specifically in the Q&A and it is the straightforward part. • A maintained upgrade-history record , also raised on the call. We would want this as structured data behind a public endpoint rather than a wiki page, so that other operators’ tooling can consume it rather than scraping it. Three questions before anyone commits to anything, because “public good” should mean something more specific than enthusiasm: • Is the configurable-upgrade-notification tool that was…

Excerpt (1193 of 2754 characters). Read the whole post on the forum ↗