Gaia v27.4.0 Upgrade
Cosmos Hub proposal #1041: # Summary - The `v27.4.0` upgrade bumps the following versions: - `cometbft` v0.38.21 → v0.38.23 - `wasmd` v0.60.6 → v0.60.7 - `wa...
Yes
100%
No
0%
Abstain
0%
Veto
0%
AI Summary
gpt-5.4-mini - generated 6/8/2026, 11:12:37 PM
Gaia v27.4.0 Upgrade
Cosmos Hub proposal 1041 asks validators to approve the Gaia v27.4.0 upgrade, which bumps CometBFT, wasmd, and wasmvm versions. It uses a seven-day voting period and, if passed, requires validators to update the Cosmos Hub binary at the scheduled upgrade height. The upgrade is described as state-breaking and mandatory after approval.
- Upgrades CometBFT from v0.38.21 to v0.38.23.
- Upgrades wasmd from v0.60.6 to v0.60.7.
- Upgrades wasmvm from v2.3.2 to v2.3.3.
- Voting period is seven days.
- Validators must upgrade the Cosmos Hub binary at the designated height if the proposal passes.
Voter Impact
A YES vote supports a required network upgrade; a NO vote rejects it. Because the upgrade is state-breaking and mandatory after passage, voters should expect coordination work for validators and potentially temporary operational risk at the upgrade height.
Risk Signals
- State-breaking upgrade means nodes must upgrade in sync or risk disruption.
- Mandatory upgrade increases operational dependence on validators following instructions.
- The proposal text gives release and changelog links, but does not summarize the underlying code changes, so some impact details are uncertain.
Original Proposal Text
# Summary - The `v27.4.0` upgrade bumps the following versions: - `cometbft` v0.38.21 → v0.38.23 - `wasmd` v0.60.6 → v0.60.7 - `wasmvm` v2.3.2 → v2.3.3 - This proposal has a voting period of **SEVEN DAYS**. - If the proposal passes, validators will be required to update the Cosmos Hub binary at the specified upgrade height. # Release Details - The release can be found [here](https://github.com/cosmos/gaia/releases/tag/v27.4.0). - The changelog can be found [here](https://github.com/cosmos/gaia/blob/v27.4.0/CHANGELOG.md). **This upgrade is state-breaking and mandatory once the on-chain vote passes and the upgrade height is reached.** # Governance votes The following items summarize the voting options and what it means for this proposal: YES - You agree that the Cosmos Hub should be updated with this release. NO - You disagree that the Cosmos Hub should be updated with this release. NO WITH VETO - A ‘NoWithVeto’ vote indicates a proposal either (1) is deemed to be spam, i.e., irrelevant to Cosmos Hub, (2) disproportionately infringes on minority interests, or (3) violates or encourages violation of the rules of engagement as currently set out by Cosmos Hub governance. If the number of ‘NoWithVeto’ votes is greater than a third of total votes, the proposal is rejected and the deposits are burned. ABSTAIN - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal. More details: ipfs://CID