Gaia v29.0.0 Software Upgrade (Update: v29.0.1 Recommended)

Hub Proposals Software Upgrade
1

Update (October 23, 2026): Gaia v29.0.1 is now recommended for the scheduled upgrade. This non-state-breaking patch release is built with Go 1.26.10, which includes a security fix for CVE-2026-111943. The on-chain upgrade name remains v29.0.0, and the upgrade height remains 33,618,500.

Voting Information

The Gaia v29.0.0 software upgrade proposal for the Cosmos Hub mainnet is now open for on-chain voting.

  • Proposal: Proposal #1059
  • Voting period: 7 days
  • Voting deadline: October 27, 2026, at 12:00 UTC

Validators and ATOM delegators are encouraged to review the proposal and cast their votes before the deadline.

Upgrade Schedule

If approved, the Cosmos Hub mainnet will execute the on-chain v29.0.0 upgrade at the following block height:

  • Upgrade height: 33,618,500
  • Estimated upgrade time: October 28, 2026, at 13:50 UTC

The estimated time may vary depending on block production.

Node operators should download and verify the Gaia v29.0.1 binary in advance and prepare to use it at the scheduled upgrade height.

Cosmovisor: Place the v29.0.1 binary at $DAEMON_HOME/cosmovisor/upgrades/v29.0.0/bin/gaiad. Keep the directory name v29.0.0 to match the on-chain upgrade plan.

Note: Operators who initially upgrade using v29.0.0 can subsequently switch to v29.0.1 by replacing the binary and restarting their nodes. No additional governance proposal or coordinated upgrade height is required.

Release Details

Gaia v29.0.0 removes the deprecated x/params module and legacy parameter APIs, cleans up obsolete state, and updates core dependencies.

Important operational note:

  • Multisig transactions: Due to a known gas simulation issue in Cosmos SDK v0.53.8, multisig senders must specify a fixed --gas value instead of using --gas auto.

For complete technical details and upgrade procedures, refer to the official documentation:

Governance Votes

The following summarizes the voting options and their meaning for this proposal:

YES - You support upgrading the Cosmos Hub to Gaia v29.0.0.

NO - You oppose upgrading the Cosmos Hub to Gaia v29.0.0.

NO WITH VETO - You consider the proposal spam or irrelevant to the Cosmos Hub, disproportionately harmful to minority interests, or contrary to the rules established by Cosmos Hub governance. If the applicable veto threshold is exceeded, the proposal is rejected, and deposits are subject to the chain’s governance deposit-burning rules.

ABSTAIN - You wish to contribute to quorum but formally decline to vote either for or against the proposal.

1 Like
Hub Weekly Update #21: October 22, 2026
2

Thanks for the clear schedule. From a wallet support perspective, two quick questions that would help us answer users:

  1. Do regular ATOM holders and delegators need to do anything for this upgrade, or is it only for node operators?
  2. Should users expect a short pause in transactions around the upgrade height, and is there anything wallets or apps should check given the removal of the legacy parameter APIs?
3

Thanks for the questions!

  1. ATOM holders and delegators: No token migration or other on-chain action is required for the upgrade itself. Delegators can vote directly on Proposal #1059. If they don’t vote, their voting power follows their validator’s vote, if cast. A delegator’s direct vote takes precedence over their validator’s vote for their delegated stake.

  2. Network downtime and wallet compatibility: If approved, block production will temporarily halt at the upgrade height. Transactions cannot be confirmed until sufficient validators complete the upgrade and consensus resumes. The downtime depends on how quickly validators complete the upgrade and restore consensus.

Validators and RPC/API providers running Gaia nodes must install the required upgrade release. Wallet and app developers should confirm their RPC providers are prepared and check for dependencies on the legacy parameter APIs being removed.

2 Likes