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 11. With Stride migrated to proof of authority, Gaia v28.0.0 removes the Hub’s now-unneeded ICS provider module. A forum post is up with the technical details, and comments are welcome there before the mainnet proposal goes out.
USDC on Injective: two-click flow in validation
The workstream is validating a two-click flow on mainnet through a limited test interface. The public one-click experience remains the target, with additional coordination and implementation work underway.
Topic of the month: validator set health
The validator-health work defines measurable desired states and response options for concentration and governance participation. The current thresholds are working targets that can be recalibrated through further analysis and ecosystem input.
Three metrics are highlighted against desired states today.
A central validator-health objective is to improve the Hub’s Nakamoto coefficient over time. The working desired state is for at least seven independent entities to be required to reach one-third of active-set voting power, supported by broader participation and stake distribution across the validator set.
The current halt coefficient is 3, meaning three entities could collectively reach the one-third voting-power threshold that can halt the chain.
The safety coefficient, the number of entities required to control consensus at the 66.667% threshold, is 16. The desired state is at least 20.
On governance turnout, the Hub requires 40% participation for quorum, and validators with voting power who do not participate make that harder to reach. The working desired state is for proposals to reach quorum with a 10 percentage-point buffer, so at a 40% quorum, 50% turnout would be considered healthy. If the quorum parameter changed, the same 10 point buffer would apply on top of it.
These feed a dashboard that calculates on chain in real time, tracking entities above 5% voting power, whether any single entity can veto a proposal, the block height each snapshot was taken at, validators at signing risk and the voting power they hold, and the state of governance proposals. The monitoring is intended to support earlier outreach when concentration, signing risk, or governance participation moves outside the desired ranges.
What is driving concentration
Validator unwinds are monitored so potential changes in stake distribution and concentration can be identified early.
Operators also discussed infrastructure-cost pressure and opportunities to compare allocated power with actual usage when negotiating data-center contracts.
Quorum
The analysis presented estimated that around 38% of current active-set voting power has historically not participated in governance, leaving limited margin above the 40% quorum. Validators discussed notification improvements and possible governance levers, without endorsing a specific parameter change. Further community input is welcome.
Validator tooling: survey results and possible public goods
The survey received five responses. Upgrade notifications and PebbleDB snapshots were the only areas supported by every respondent, while three respondents also wanted reliable historical and indexed data. Three respondents said they could operate a public-good service, and the ecosystem team will follow up.
The call demonstrated three tools being considered for open-source release: configurable upgrade notifications, PebbleDB snapshots with upgrade-height support, and a self-hostable CosmWasm explorer. Operator feedback will help determine which tools move forward.
Q&A themes
Validators discussed governance participation, including the legal and operational constraints that can prevent some operators from voting, whether a longer voting window would materially improve turnout, and whether other ways to represent non-participation deserve further study. No specific governance change was endorsed.
Validators also requested email as an additional upgrade-notification channel and confirmed that a maintained upgrade-history record would be useful. These inputs will inform future tooling work.
Next steps
The next validator call will occur on September 9 at 9:00 AM ET. If you are an active set validator and have not yet joined the channel, message @totalspud or @robomcgobo on Telegram for an invite.