-
Notifications
You must be signed in to change notification settings - Fork 2
feat: admin functions #393
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: admin functions #393
Conversation
…lidator-upgradeability-2 Signed-off-by: Chiin <[email protected]>
…in-functions Signed-off-by: Chiin <[email protected]>
0xOneTony
left a comment
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.
I noticed we set the voting cycle data on initiallization but I dont think this is needed, wdyt?
| { | ||
| _setMinimumVotingPower(_minimumVotingPower); | ||
| _setVotingCycleBlock(_votingCycleBlock); | ||
| _setVotingCycleData(_cycleNumber, _startBlock, _duration, _votingCycleDistributionLimit); |
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.
Do we need to set the voting cycle data on initiallization?
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.
I'd recommend keeping it as it is required for moving to vote any proposal. This is being further discussed internally regarding how the logic will be done. I prefer to keep this for the moment
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.
thinking more about this maybe we can keep it and even if no cycle is active or planned we could always use the previous one i guess
* feat: add upgradeability to ProposalValidator contract * chore: fix styling * feat: add admin functions and tests * chore: more descriptive variables naming * test: expect event emissions * test: use fuzzing for setter functions * chore: run pre-pr * docs: use correct natspec in ProosalValidator contract * feat: add semver * feat: add reinitializable base * chore: run pre-pr * chore: run pre-pr --------- Signed-off-by: Chiin <[email protected]>
* feat: add upgradeability to ProposalValidator contract * chore: fix styling * feat: add admin functions and tests * chore: more descriptive variables naming * test: expect event emissions * test: use fuzzing for setter functions * chore: run pre-pr * docs: use correct natspec in ProosalValidator contract * feat: add semver * feat: add reinitializable base * chore: run pre-pr * chore: run pre-pr --------- Signed-off-by: Chiin <[email protected]>
No description provided.