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
Note: not every field is correctly named. Please update the field names as we come across the correct names.
The comet team is building out a really neat configuration reference manual that I think will be helpful in determing an ideal configuration for eve's genesis parameters:
Goal: heavily penalize equivocation, while not even bothering to slash for downtime, but instead ensure that validators are removed from consensus to allow the chain to function ideally and reduce the risk of a halt.
Goal: minimize the role of governance on Eve, while ensuring that governance functions well for the few key activities where it's essential:
chain upgrades
community pool funding
taxation (tax is initally set to zero)
light client updates
formation and dissolution of alliances
onboarding and offboarding consumer chains
quorum: 40% of staked tokens must vote
pass threshold: 2/3rds yes
Veto: let's try to disable it, we don't need veto because the pass threshold is 2/3rds
Staking
Minimum inflation = 10%
Maximum inflation = 35%
target_bonded_rate = 75%
VALIDATORS: 300
MINIMUM COMMISSION: 11.69420808%
Eve has no maximum supply concept. She'll inflate over time, and that is fine. Track market cap, not unit price (duh)
Additional Configuration
Interchain accounts
We should attempt to block liquid staking chains that do not allow validator choice from connecting to Eve.
Stargeate Queries
If we feel that it is safe to do so, let's configure stargate queries as * to allow contract devleopers maximum configuratbility when using eve.
Block Time
Eve should attempt to make 2 second blocks. She won't always succeed, but the extra responsiveness will allow for a wide range of use cases that other chains cannot accomodate. It is perfectly reasonable to look into reducing block times to 1 second, but we should not spend a lot of time on that, and it may not be possible.
The text was updated successfully, but these errors were encountered:
Eve's genesis Parameters
Note: not every field is correctly named. Please update the field names as we come across the correct names.
The comet team is building out a really neat configuration reference manual that I think will be helpful in determing an ideal configuration for eve's genesis parameters:
the parameters
Comet
max_bytes: 2000000
max_gas: 100000000
Cosmos-sdk
Parameters for the cosmos-sdk
Slashing
Goal: heavily penalize equivocation, while not even bothering to slash for downtime, but instead ensure that validators are removed from consensus to allow the chain to function ideally and reduce the risk of a halt.
slashing_jail_window: 1000 blocks
downtime slash: 0%
equivocation slash: 10%
Governance
Goal: minimize the role of governance on Eve, while ensuring that governance functions well for the few key activities where it's essential:
quorum: 40% of staked tokens must vote
pass threshold: 2/3rds yes
Veto: let's try to disable it, we don't need veto because the pass threshold is 2/3rds
Staking
Minimum inflation = 10%
Maximum inflation = 35%
target_bonded_rate = 75%
VALIDATORS: 300
MINIMUM COMMISSION: 11.69420808%
Eve has no maximum supply concept. She'll inflate over time, and that is fine. Track market cap, not unit price (duh)
Additional Configuration
Interchain accounts
We should attempt to block liquid staking chains that do not allow validator choice from connecting to Eve.
Stargeate Queries
If we feel that it is safe to do so, let's configure stargate queries as * to allow contract devleopers maximum configuratbility when using eve.
Block Time
Eve should attempt to make 2 second blocks. She won't always succeed, but the extra responsiveness will allow for a wide range of use cases that other chains cannot accomodate. It is perfectly reasonable to look into reducing block times to 1 second, but we should not spend a lot of time on that, and it may not be possible.
The text was updated successfully, but these errors were encountered: