You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently use the default params of most modules. We should settle on which params we want to launch with.
Problem Definition
The defaults might not be the best choices for Celestia. Also, changing a param might cause more friction if they are not modifiable via governance (see: #168).
While the genesis params could also be defined in the networks repository before launch, I would suggest discussing the parameters in here and maybe have a genesis file (with these decided on parama) we can use as a basis too.
While this could wait until launch, I suggest to prioritize this to have the next testnet with params as close as possible to the launch params.
The text was updated successfully, but these errors were encountered:
Summary
We currently use the default params of most modules. We should settle on which params we want to launch with.
Problem Definition
The defaults might not be the best choices for Celestia. Also, changing a param might cause more friction if they are not modifiable via governance (see: #168).
Proposal
Decide on each parameter.
Most important ones include inflation, token name, max validators at launch. An non-exhaustive list can be found here:
https://github.com/gavinly/CosmosParametersWiki/blob/master/param_index.md
Most of the parameters are now also described in the docs of each module as well (example: https://github.com/cosmos/cosmos-sdk/blob/master/x/staking/spec/08_params.md).
While the genesis params could also be defined in the networks repository before launch, I would suggest discussing the parameters in here and maybe have a genesis file (with these decided on parama) we can use as a basis too.
While this could wait until launch, I suggest to prioritize this to have the next testnet with params as close as possible to the launch params.
The text was updated successfully, but these errors were encountered: