-
Notifications
You must be signed in to change notification settings - Fork 2
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
Governance #153
Comments
In DAODAO, voting power is determined by the "voting power module". We could write our own voting power module that essentially just reads peoples voting power in Hydro, and by that, we should technically be able to just have a DAODAO instance that uses the same voting powers as Hydro, but can do all the things a DAODAO multisig can. In particular, we could have that for pausing, unpausing, adjusting the max locked tokens, etc. |
initially the hydro governance should just be used for 1-off props like:
|
Spike: Write a voting power module that takes voting powers from the Hydro contract and deploy a DAODAO instance with voting powers taken from Hydro |
One potential complexity is that the Hydro contract needs to be refactored to use snapshot maps for total powers and user voting powers. Since we keep voting powers in a "future looking manner", this also requires computing the round_id a certain height corresponds to (since the DAODAO voting power module queries voting powers by height). |
Reference: the DAODAO voting power module is explained here: https://github.com/DA0-DA0/dao-contracts/wiki/DAO-DAO-Contracts-Design#the-voting-module |
We want to enable Hydro voters to participate in governance of the Hydro protocol and eventually take on the role of the Hydro DAO.
In the first step, this would need just text proposals to represent decisions of the community on the protocols direction.
The text was updated successfully, but these errors were encountered: