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
There's several consensus timing fields in the config file (in config.toml) that we'd like to standardize across nodes.
Problem Definition
We see a lot of sporadic block times and it's possibly related to various consensus. settings which each node can define for itself.
Proposal
There's a couple things we can do depending on how much effort we want to put in.
(low effort) Hard-code the values in our config management stuff. This will involve providing the hard-coded values to viper.
(more effort) Create some new params to hold them and store them somewhere. Set them in the next upgrade, and provide endpoints for getting and setting-via-gov-prop.
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged
Contributor assigned/self-assigned
The text was updated successfully, but these errors were encountered:
Summary
There's several
consensus
timing fields in the config file (inconfig.toml
) that we'd like to standardize across nodes.Problem Definition
We see a lot of sporadic block times and it's possibly related to various
consensus.
settings which each node can define for itself.Proposal
There's a couple things we can do depending on how much effort we want to put in.
For Admin Use
The text was updated successfully, but these errors were encountered: