-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat!: support for custom proposal-based voting periods #239
Conversation
Will fix tests shortly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Nit(we can also create an issue and set this as a chore): I wish there was more test cases added, other than simply comparing the two proposals, but don't want to block merging for this!
@mattverse I added |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, looks good to me!
We shouldn't need to initialize the new param in our app.go right, since this doesn't update the paramset, just the concrete struct at VotingParams
?
That's correct! |
This is super cool guys! |
* feat: custom proposal-based voting periods (#1) h/t osmosis-labs#239 * feat: expedited proposals (#2) * feat: expedited proposals h/t osmosis-labs#240 * fix: correctly generate random threshold params * fix: update randomised genesis state tests * feat: allow protocol stakers and delegators to vote (#3) * feat: expedited deposits (#4) h/t osmosis-labs#254 * fix: still include custom voting periods * fix: fallback to custom voting periods
Add support for custom voting periods:
ProposalVotingPeriod
[]ProposalVotingPeriod
to the existingVotingParams
(on-chain upgrade should be fine)Keeper#ActivateVotingPeriod
to account for the new[]ProposalVotingPeriod
NOTE: I did NOT add/implement
CustomVotingPeriodQuorum
as I just didn't see that as necessary.ref: osmosis-labs/osmosis#1517