Skip to main content
This page answers one question before every other page: which versions you are dealing with. Read it before you install. Come back to it whenever a page in the Cosmos SDK or CometBFT sections looks different from what your node does.

Mainnet

The release to run on the Cosmos Hub mainnet, chain-id cosmoshub-4, is gaia v29.0.1.
Any public remote procedure call (RPC) endpoint returns the application version its node runs. Compare two providers if the answer surprises you. On 2026-11-08 this returned v29.0.1 at height 33789237. The chain moved to v29 at height 33618500 on 2026-10-28, through governance proposal 1059 (upgrade name v29.0.0). The v29.0.1 release notes tell operators to run v29.0.1 for that upgrade. It is the same upgrade built with a newer Go toolchain. Upgrade history lists every upgrade. Build or download v29.0.1. Confirm the same numbers from your own binary:
The first command prints the gaia, Cosmos SDK, and Go versions. The second lists the dependency lines that carry the CometBFT, PebbleDB, ibc-go, and wasmd versions.

Testnet

The public testnet, chain-id provider, runs the release candidate that will reach mainnet next. On 2026-11-08 it ran gaia v29.1.0-rc0, upgraded at height 19696000 on 2026-11-03 through testnet proposal 332.
The testnet is where operators rehearse upgrades. The current state of the testnet, the next planned upgrade, and the join scripts are in the cosmos/testnets provider README. The Join testnet page walks through it.

Facts that depend on the version

  • The Hub currently runs Cosmos SDK v0.53 staking. gaia v29.0.1 has no command to rotate a validator key: gaiad tx staking --help lists cancel-unbond, create-validator, delegate, edit-validator, redelegate, and unbond only. The operator key can never be changed. The consensus key has no rotation path on the Hub. The node key is simply regenerated when needed.
  • The gaiad config command is confix v0.1.2. Setting a config.toml key needs gaiad config set config <key> <value> -s. Without -s, confix answers cometbft config is not supported. App keys work without it: gaiad config set app <key> <value>.
  • The database backend defaults to goleveldb. PebbleDB is built in (pebbledb). See Database backends.
  • The --x-crisis-skip-assert-invariants flag is gone. The pruning-keep-every option is gone. Both still appear in old guides.
  • The x/params module is gone in v29. There is no gaiad query params command and no cosmos.params.v1beta1.Query service. Each module keeps its own parameters, read with gaiad query <module> params and changed by a governance proposal carrying that module’s MsgUpdateParams. The legacy ParameterChangeProposal route is gone. See Parameter change proposals.
  • On v29.0.x, 21 old proposals (the newest is 868) carry ParameterChangeProposal content the node can no longer decode. Any query that reads one of them fails with no concrete type registered for type URL /cosmos.params.v1beta1.ParameterChangeProposal. That includes gaiad query gov proposals with a --proposal-status filter. Read recent proposals with gaiad query gov proposals --page-reverse --page-limit 20 instead. gaia v29.1.0 restores decoding. It is on the testnet and has not reached mainnet.
  • On Cosmos SDK v0.53.8, --gas auto does not work for a transaction from a multisig account. Pass a fixed --gas value. Single-key accounts are not affected.
  • The upgrade handlers compiled into v29.0.1 cover v29_0_0 only. Older upgrades require older binaries. See Upgrade history.

Which upstream docs apply

The Cosmos SDK and CometBFT sections of this site document their newest releases, which are ahead of what the Hub runs. The table says which copy to read for each operator topic. Concept pages are safe on the newest copy. Configuration references are not, so they point at the archived copy that matches the Hub.

Verify

Prints v29.0.1 for a mainnet binary built from the current tag. If your binary prints a different version, it is either an older release or a testnet release candidate.

Next

System requirements, then Install gaiad.