protocols
Cosmos Hub votes on Gaia v29.1.0 to restore governance queries
Voting on Proposal 1061 runs through November 17 at 11:57 UTC. It calls for a coordinated upgrade to restore access to historical proposals and allow the chain’s state to be exported.

Twenty-one historical proposals are affected
Cosmos Hub voters are considering an upgrade to the Gaia software that would restore access to part of the network’s governance archives. Proposal 1061, discussed on the November 11, 2026 validator call, remains open until November 17 at 11:57 UTC. If it passes, Gaia v29.1.0 is scheduled for block 33,935,300, which the call organizers then expected around November 18. The block height determines when the upgrade takes effect. The date is an estimate.
The problem dates back to the October 28 upgrade. Version 29 removed the legacy parameter-management module in preparation for Cosmos SDK 0.55. Twenty-one historical proposals retain a format that this version can no longer decode. According to Hub Unit’s November 5 recap, some queries have since returned a 500 error. Block production, voting, and proposal execution continued to work.
Lists, vote tallies, and state export are affected
Errors can affect the full list of proposals, lists filtered by status, and lookups and vote tallies for certain historical proposals. State export through gaiad, the program that runs Cosmos Hub nodes, is also affected. An explorer that queries the chain to display its history can therefore receive an error when a query reaches one of these entries, even as current votes continue.
Hub Unit said that reverse pagination, which retrieves proposals from newest to oldest, offered a workaround for tools that support it. This lets tools reach recent entries first. Gaia v29.1.0 restores decoding of historical parameter-change proposals so the queries can also process those entries and the chain’s state can be exported again.
A coordinated upgrade at block 33,935,300
The version has already been tried on the test network, according to the validator call recap. Installing it on mainnet requires a coordinated upgrade because it changes the chain’s state. If the proposal passes, validators will need to run the new binary at the scheduled height. Activation thus depends on the outcome of the vote and the network reaching the designated block.
Release notes in the Gaia repository also describe two CosmWasm updates: wasmd moves from 0.60.9 to 0.60.10 and wasmvm from 2.3.5 to 2.3.6. Those updates accompany the governance query fix. For explorer and API operators, the practical change to check after a possible activation will be whether requests that fail on the historical entries work again.
