The Ledger
Cosmos Hub Approves Gaia v29 Upgrade for Block 33,618,500
Cosmos Hub governance approved Proposal 1059 to upgrade the network to Gaia v29, targeting block 33,618,500 on October 28. The change removes the legacy x/params module, while node operators are directed to use the v29.0.1 binary.

“The upgrade is state-breaking, and validators will need to switch binaries at the upgrade height.”
RoboMcGobo, in a Hub Unit weekly update
Cosmos Hub governance approved Proposal 1059 for the Gaia v29 software upgrade on October 27, with the network change scheduled for block 33,618,500 on October 28. The Hub’s upgrade post estimates the target at 13:50 UTC and cautions that the time can shift with block production. The approval settles the governance question; validators still need to carry out the coordinated software change at the designated height.
Gaia v29 retires the Hub’s legacy parameter route
The release removes the deprecated x/params module, along with the legacy ParameterChangeProposal governance route and the cosmos.params.v1beta1.Query service. After the change, parameter adjustments go through the governance messages belonging to each module, according to the Hub Unit’s upgrade summary.
Gaia v29 also updates the Cosmos SDK from v0.53.4 to v0.53.8 and Go from 1.25 to 1.26. The Hub Unit said the release had been running on the provider testnet since October 13, ahead of the mainnet vote. Those changes make this a state-breaking upgrade, rather than a routine binary replacement that operators can roll out without coordinating around a block height.
Operators should install v29.0.1, not v29.0.0
The governance plan retains the on-chain upgrade name v29.0.0, but the recommended binary changed before the scheduled activation. The Gaia team’s v29.0.1 release notes direct operators to use that patch at block 33,618,500; the release rebuilds Gaia with Go 1.26.10 and includes a crypto/x509 security fix.
For operators using Cosmovisor, the forum instructions place the binary in the upgrades/v29.0.0/bin directory, matching the on-chain plan name. Gaia’s release notes say nodes already running v29.0.0 can switch to v29.0.1 by replacing the binary and restarting, without another governance proposal.
Multisig transactions need a fixed gas limit
The upgrade also carries an operational caveat for multisig users. In Cosmos SDK v0.53.8, automatic gas simulation with --gas auto is broken for multisig senders, so the Hub and Gaia release notes instruct them to specify a fixed --gas value until an upstream fix is available.
ATOM holders and delegators do not need to migrate tokens or take another on-chain action for the upgrade itself, according to the forum post. Delegators can vote directly on proposals; if they do not, their voting power follows their validator’s vote when one is cast. The post says block production will temporarily halt at the upgrade height, leaving transactions unconfirmed until enough validators install the release and consensus resumes.
The practical dividing line is clear: validators and node operators must prepare for the block-height change, while wallet and app developers should check whether their services depend on the retiring parameter API. The Hub’s announced target is block 33,618,500, and its recommended executable is Gaia v29.0.1.
Sources
- Original source Cosmos Hub Forum · Gaia v29 software upgrade update v29 recommended forum.cosmos.network
Other pages read
- Cosmos/gaia on GitHub github.com
- Cosmos Hub Forum · Hub weekly update october forum.cosmos.network
- Plebis Governance Platform pleb.is