Cosmos Hub is running Gaia v29.0.1 after its validators crossed the state-breaking upgrade height on October 28, removing a legacy system for changing network parameters and moving the chain onto newer core software.
The activation is visible in Polkachu’s Cosmos Hub upgrade history, checked October 29: it lists block 33,618,500 under v29.0.1 and identifies v29.0.1 as the current node version. Blockdaemon separately marked its Cosmos node upgrade complete at 16:15 UTC on October 28. That status applies to Blockdaemon’s infrastructure, not every validator, so it corroborates the transition without establishing an exact network-wide restart time.
The distinction matters. Governance approval and a scheduled height do not prove that a coordinated blockchain upgrade completed. Here, the post-event node record establishes that the Hub moved past the trigger height on the new release, while the available records do not quantify how long consensus paused or how many validators upgraded on time.
What Gaia v29 changes
Proposal 1059 scheduled the transition at block 33,618,500. The approved v29.0.0 plan removes the deprecated `x/params` module, the old `ParameterChangeProposal` route and the associated legacy query service. Parameter changes now have to use governance messages owned by the relevant module instead of a common, older parameter store.
That is infrastructure housekeeping with a governance consequence: applications and operational tools that still query the retired interface need to adapt. It does not change ATOM balances, create a token swap or give holders a migration task. The Cosmos Hub forum explicitly said ordinary ATOM holders and delegators did not need to take an on-chain action for the upgrade itself.
The release also moves the Hub’s Cosmos SDK dependency from v0.53.4 to v0.53.8 and its Go toolchain from the 1.25 line to the 1.26 line. Those version changes are documented in the proposal record; they should not be read as measurements of faster transactions, higher capacity or better economic performance. No post-upgrade benchmark was published in the reviewed source packet.
Why validators used v29.0.1
The on-chain upgrade kept the name v29.0.0, but maintainers told operators to install v29.0.1 at the scheduled height. The patch was released October 23 and rebuilt Gaia with Go 1.26.10, which incorporated a `crypto/x509` security fix. Maintainers described v29.0.1 as non-state-breaking, meaning nodes already on v29.0.0 could replace the binary and restart without another governance proposal.
This naming mismatch is operationally important. A validator following only the plan name could reasonably expect a v29.0.0 binary, while the maintained release record recommends v29.0.1. The primary documentation resolves that ambiguity and provides signed release artifacts and verification instructions.
One known limitation remains. The Cosmos Hub forum says automatic gas simulation is broken for multisig senders under the included Cosmos SDK release. Multisig operators must specify a fixed gas value until the upstream issue is corrected. That warning concerns transaction construction; it is not evidence of lost funds or a consensus failure.
What remains unmeasured
The verified milestone is narrower than a claim that the upgrade improved the network. The chain crossed its governed height, current infrastructure reports v29.0.1, and the legacy parameter module is no longer part of the active release. The reviewed records do not provide an independently measured consensus-pause duration, validator participation rate, transaction-throughput comparison or application-compatibility audit.
Those are the next checks. A later assessment should compare block timing around the upgrade, identify any validators that remained offline, and test whether wallets, explorers and governance tools have removed dependencies on the retired APIs. Until then, Gaia v29 is best described as a completed software and governance transition, not proof of improved performance or demand for ATOM.
The complete source packet and revision history are retained with the newsroom record.
Automated systems may have assisted with source organization and drafting. Coinburn is accountable for the published text and maintains a revision record.
This article provides news and analysis, not investment, legal or tax advice. Digital assets are volatile and may result in total loss.