What parameters can be changed?
The complete parameters of the Cosmos Hub are split up into different modules, each of which has its own set of parameters. Most parameters can be updated by submitting a governance proposal. List of modules whose parameters can be changed via governance:- x/auth
- x/bank
- x/distribution
- x/evidence
- x/feegrant
- x/gov
- x/mint
- x/slashing
- x/staking
- ibc-go/transfer
- interchain-security/provider
MsgUpdateParams for providing parameter changes. You can learn more about it in the cosmos-sdk documentation of each module (e.g. Link)
What are the current parameter values?
There are ways to query the current settings for each module’s parameter(s). Some can be queried with the command line programgaiad.
You can begin by using the command gaiad q [module] -h to get help about the subcommands for the module you want to query. For example, gaiad q staking params returns the settings of relevant parameters:
bank module’s parameter, which is sendenabled. You also cannot query the crisis module’s parameters.
Why create a parameter change proposal?
Parameters are what govern many aspects of the chain’s behaviour. As circumstances and attitudes change, sometimes you might want to change a parameter to bring the chain’s behaviour in line with community opinion. For example, the Cosmos Hub launched with 100 active validators and there have been 4 proposals to date that have increased theMaxValidators parameter. At the time of writing, the active set contains 180 validators.
The Cosmos Hub has been viewed as a slow-moving, highly secure chain and that is reflected in some of its other parameters, such as a 21 day unbonding period and 14 day voting period. These are quite long compared to other chains in the Cosmos Ecosystem