> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cosmos.network/llms.txt
> Use this file to discover all available pages before exploring further.

# Versions

> For operators who need to know exactly what the Cosmos Hub runs today and which Cosmos SDK, CometBFT, and IBC documentation applies to it.

Commands on this page were run on gaia v29.0.1 (Cosmos SDK v0.53.8, CometBFT v0.38.25) on 2026-11-08 by agent testing on a local devnet.

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.1.0.

```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
curl -s https://cosmos-rpc.polkachu.com/abci_info | jq -r '.result.response.version'
```

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. The chain moved to v29.1.0 at height 33935300, through governance proposal 1061; voting ended 2026-11-17. [Upgrade history](https://docs.cosmos.network/hub/latest/upgrade/history.md) lists every upgrade. Build or download v29.1.0.

| Component | Version in gaia v29.1.0 | Where it is pinned |
| - | - | - |
| gaia | v29.1.0 (released 2026-11-09) | [release page](https://github.com/cosmos/gaia/releases/tag/v29.1.0) |
| Cosmos SDK | v0.53.8 | `go.mod` |
| CometBFT | v0.38.25 | `go.mod` |
| cometbft-db | v1.0.4, with cockroachdb/pebble v1.1.5 | `go.mod` |
| ibc-go | v10.7.0, with 08-wasm v10.5.0 | `go.mod` |
| wasmd | v0.60.10, with wasmvm v2.3.6 | `go.mod` |
| feemarket | v1.1.2 pre-release | `go.mod` |
| confix (the `gaiad config` command) | v0.1.2 | `go.mod` |
| Go | 1.26.10 | `go.mod` and the release Dockerfile |

Confirm the same numbers from your own binary:

```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
gaiad version --long | grep -E '^(version|cosmos_sdk_version|go):'
gaiad version --long | grep -E 'cometbft/cometbft@|cockroachdb/pebble@|ibc-go/v10@|CosmWasm/wasmd@'
```

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.

```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
curl -s https://rpc.provider-sentry-01.hub-testnet.polypore.xyz/abci_info | jq -r '.result.response.version'
```

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](https://github.com/cosmos/testnets/blob/master/provider/README.md). The [Join testnet](https://docs.cosmos.network/hub/latest/hub-tutorials/join-testnet.md) page walks through it.

## Facts that depend on the version

* The Hub currently runs Cosmos SDK v0.53 staking. gaia v29.1.0 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](https://docs.cosmos.network/hub/latest/node/database.md).
* 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](https://docs.cosmos.network/hub/latest/governance/proposal-types/param-change.md).
* 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.
* 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.1.0 cover `v29_1_0` only. Older upgrades require older binaries. See [Upgrade history](https://docs.cosmos.network/hub/latest/upgrade/history.md).

## 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.

| Topic | Read this | Why |
| - | - | - |
| Cosmovisor | [Cosmovisor](https://docs.cosmos.network/sdk/latest/guides/upgrades/cosmovisor.md) | Cosmovisor v1.7.3 is independent of the SDK version. Skip anything about `--verbose_log_level` or ML-DSA keys |
| confix (`gaiad config`) | [confix](https://docs.cosmos.network/sdk/latest/guides/tooling/confix.md) | Same tool, same commands |
| Keyring | [Keyring](https://docs.cosmos.network/sdk/latest/node/keyring.md) | Backends and flags unchanged |
| Running a node | [Run a node](https://docs.cosmos.network/sdk/latest/node/run-node.md) | Concepts apply; use the Hub pages for the exact commands |
| Production checklist | [Run in production](https://docs.cosmos.network/sdk/latest/node/run-production.md) | Concepts apply |
| Remote signing with Cosmos KMS | [Remote signing](https://docs.cosmos.network/sdk/latest/kms/remote-signing.md) | Cosmos KMS v0.1.0 has one copy; see also [Remote signing on the Hub](https://docs.cosmos.network/hub/latest/validators/remote-signing.md) |
| Upgrade module | [Upgrade module](https://docs.cosmos.network/sdk/latest/modules/upgrade/README.md) | Plan, applied, and module-versions queries are the same on v0.53 |
| Validator key rotation pages | None | Those pages describe features the Hub does not run |
| CometBFT configuration reference | [Configuration (v0.38)](https://docs.cosmos.network/cometbft/v0.38/docs/core/configuration.md) | The newest copy documents a different config file |
| CometBFT mempool | [Mempool (v0.38)](https://docs.cosmos.network/cometbft/v0.38/docs/core/mempool.md) | Same reason |
| CometBFT running in production | [Running in production](https://docs.cosmos.network/cometbft/latest/docs/core/Running-in-production.md) | Concepts apply |
| CometBFT validators and sentries | [Validators](https://docs.cosmos.network/cometbft/latest/docs/core/Validators.md) | Concepts apply |
| CometBFT state sync | [State sync](https://docs.cosmos.network/cometbft/latest/docs/core/state-sync.md) | Concepts apply; Hub values are on [Sync a node](https://docs.cosmos.network/hub/latest/node/sync.md) |
| CometBFT metrics | [Metrics](https://docs.cosmos.network/cometbft/latest/docs/core/metrics.md) | Metric names match v0.38 closely; see [Monitoring](https://docs.cosmos.network/hub/latest/validators/monitoring.md) |
| IBC relayers | [Relayer](https://ibcprotocol.dev/docs/ibc-go/latest/ibc/relayer) | ibc-go v10 is current; see [Relaying](https://docs.cosmos.network/hub/latest/infrastructure/relaying.md) |

## Verify

```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
gaiad version
```

Prints `v29.1.0` 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](https://docs.cosmos.network/hub/latest/getting-started/system-requirements.md), then [Install gaiad](https://docs.cosmos.network/hub/latest/getting-started/installation.md).
