app/modules.go in the release, so operators and builders can see which messages and parameters exist on chain. Each module’s current parameters come from the query shown next to it (all queries below ran against mainnet on 2026-10-15). Module documentation is kept with the module’s source. The Hub pages only cover what the Hub configures differently.
Three modules that older lists mention are not in v28.3.1: the interchain security provider (removed in v28.0.0, as the Hub no longer hosts consumer chains), ICS-29 fee middleware, and the globalfee module (replaced by the fee market). The gaiad q upgrade module-versions query still reports capability and crisis entries from earlier versions. Neither has state or messages any more.
Cosmos SDK v0.53.4
ibc-go v10.7.0
The transfer application is wrapped as transfer, then callbacks, then rate limiting, then packet forward middleware on the classic stack. On the v2 stack it is wrapped as transfer, callbacks, and rate limiting (
app/keepers/keepers.go).
CosmWasm (wasmd v0.60.9)
The
gaiad q wasm list-code query returned more than 100 code IDs on 2026-10-15 (the query paginates). Contracts can call the tokenfactory module through its wasm bindings.
Hub specific and third party
Verify
The authoritative list for any release is the module manager inapp/modules.go at that tag, and the versions the chain has stored:
capability, crisis).
Next
- Parameter change proposals to change any value above.
- Liquid staking, Tokenfactory, and Fee market for the Hub specific modules.