Cosmos Hub Activates v29 Upgrade, Dropping Legacy Params Module
Validators switched to Gaia v29 at block 33,618,500 on October 28, removing the legacy x/params module and moving the Hub to Cosmos SDK v0.53.8.
Key Takeaways
- The Cosmos Hub activated the Gaia v29 upgrade at block 33,618,500 on October 28, 2026.
- Governance proposal 1059 passed on October 27 with about 99.4% of the vote in favor.
- Gaia v29 removes the legacy x/params module and moves the Hub to Cosmos SDK v0.53.8 and Go 1.26.
- Node operators run the v29.0.1 binary, which rebuilds Gaia with Go 1.26.10 and a fix for a crypto/x509 vulnerability.
Update, October 28, 2026: The Cosmos Hub activated the Gaia v29 upgrade at block 33,618,500 on October 28, 2026, at about 14:15 UTC. The chain kept producing blocks on the new Gaia binary.
The Cosmos Hub, the network behind Cosmos (ATOM), activated its Gaia v29 upgrade at block 33,618,500 on October 28, 2026, after governance proposal 1059 passed on October 27 with about 99.4% of the vote in favor. The upgrade removes the legacy x/params module and moves the Hub to Cosmos SDK v0.53.8 and Go 1.26.
What the Gaia v29 Upgrade Changes
The v29 release is a state-breaking core upgrade, according to the Gaia v29.0.1 release notes in the Cosmos Hub's official repository. It removes the legacy x/params module together with the old ParameterChangeProposal route, and rebuilds the chain on Cosmos SDK v0.53.8 and Go 1.26. The follow-up v29.0.1 patch rebuilds Gaia with Go 1.26.10, which includes a fix for a crypto/x509 vulnerability. Node operators could run either binary at the upgrade height. The change keeps the Hub in step with the current Cosmos SDK generation used across the Cosmos ecosystem.
When Did the Cosmos Hub v29 Upgrade Go Live?
Proposal 1059 closed on October 27, 2026 at 12:01 UTC and passed with about 99.4% of the vote in favor, according to the Hub's on-chain governance record. The upgrade triggered at block 33,618,500 on October 28 at about 14:15 UTC, and the chain continued on the new Gaia binary. The same code had been running on the Hub's testnet since October 13. Validators and node operators switched to the new Gaia binary at the upgrade height. The Hub is one of the layer-1 blockchains that route core changes through on-chain governance votes. The upgrade later broke some governance queries, which Gaia v29.1.0 is set to fix.
What ATOM Holders and Exchanges Are Doing
The upgrade does not involve a token swap. Traders can follow the Cosmos price chart through the switch. Korean exchanges Upbit and Coinone told users they would pause ATOM deposits and withdrawals during the upgrade window, with Coinone's notice starting October 28 at 18:00 KST. In November, Cosmos handed the IBC protocol to the Linux Foundation.
Frequently Asked Questions
When Did the Cosmos Hub v29 Upgrade Go Live?
Gaia v29 activated at block 33,618,500 on October 28, 2026, at about 14:15 UTC. Governance approved the upgrade on October 27.
What Does the Cosmos Hub v29 Upgrade Change?
It removes the legacy x/params module and the old ParameterChangeProposal route, and moves the Hub to Cosmos SDK v0.53.8 and Go 1.26.
Did the Cosmos Hub v29 Upgrade Succeed?
Yes. The Hub reached the upgrade height on October 28, 2026 and kept producing blocks on the new Gaia binary.
Do ATOM Holders Need to Do Anything for the v29 Upgrade?
No. The upgrade did not involve a token swap. Validators and node operators switched to the new Gaia binary at the upgrade height.
Did Cosmos Hub Proposal 1059 Pass?
Yes. Proposal 1059 closed on October 27, 2026 at 12:01 UTC with about 99.4% of the vote in favor.
Sources
- Gaia v29.0.1 Release Notes · cosmos/gaia GitHub
- Cosmos Hub v29 upgrade instructions · Cosmos Hub on X
- Cosmos (ATOM) deposit and withdrawal suspension notice · Coinone
- Cosmos Hub block 33,618,500 · Mintscan
- Prices and market data · Coinranking