Proposals of #275

Use Skip Tendermint By Default

Exec Legacy Content
passed
Expected result
Turnout / Quorum
98.86% / 33.40%
Voting start 2023.03.17 at 18:03:19
Voting end 2023.03.22 at 18:03:19
68.12%
27 353 470 juno
Yes
7.53%
3 025 037 juno
No
0.01%
3 697 juno
Veto
24.33%
9 770 461 juno
Abstain

Details

logo
Proposer
-
Total deposit
1 000 juno
Submit time
2023.03.17 at 17:03:53
Deposit end time
2023.03.27 at 18:03:53

Description

Skip Tendermint By Default in Juno\n\nCommonwealth Discussion\n\nJuno has the highest adoption of Skip in Cosmos. To simplify validator operations, this proposal, if passed, signals for the Juno binary use Skip by default. This approach has been tested by Notional while comparing Tendermint and comet, and there is no operational difference.\n\nUsing Skip by default does not require validators to use Skip (opt-in), it purely just uses their implementation by default for validators who do use Skip. Each validator will still have the option to use skip or not, as they choose.\n\n---\n\n## Will other MEV providers be considered?\n\nRight now, Skip MEV is the leading MEV provider in Cosmos. If another provider comes up and validators decide to switch to it, governance can always be used to change to the new MEV provider by default. This is more of a QOL addition for validators, which just ensures those who use it have it pre-installed during upgrades. Validators can continue to use other MEV solutions if they choose.\n\n## How will this MEV build be integrated into the Juno codebase?\n\nIt will be replaced in the go.mod from standard Tendermint to Skip's version. You can find a PR of this here.\n\n\n\n## Voting Options\n\nYES: Agree to proceed with using Skip Tenmdermint by default.\n\nNO: Disagree with using Skip Tenmdermint by default.\n\nNO WITH VETO: Disagree with using Skip Tenmdermint by default and want depositors penalized.\n\nABSTAIN: Decline to give an opinion on using Skip Tenmdermint by default.\n\n

Votes

Voter
Answer