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
0%
No
0%
Abstain
0%
Veto
0%
AI Summary
gpt-5.4-mini - generated 6/5/2026, 3:41:50 AM
Gaia v27.4.0 Upgrade
Cosmos Hub proposal 1041 asks validators to approve Gaia v27.4.0, a mandatory, state-breaking upgrade. It updates cometbft, wasmd, and wasmvm versions and requires binary updates at the specified upgrade height if passed. Voting lasts seven days.
- 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.
- If approved, validators must update the Cosmos Hub binary at the upgrade height.
- The upgrade is state-breaking and mandatory after passage and at the upgrade height.
Voter Impact
A YES vote supports the network upgrade and required validator software changes. NO opposes the upgrade. ABSTAIN counts toward quorum without taking a side. NO WITH VETO is meant for spam or governance-rule violations and can reject the proposal if it reaches over one-third of total votes.
Risk Signals
- State-breaking upgrade creates execution risk if validators do not upgrade on time.
- Mandatory binary update may cause downtime or chain disruption for unprepared operators.
- Changelog details are external; the proposal text itself does not specify all functional changes.
- Seven-day voting window is short, so operational review time may be limited.
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