Skip to content
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

Open
p-offtermatt opened this issue Oct 16, 2024 · 3 comments
Open

Governance #153

p-offtermatt opened this issue Oct 16, 2024 · 3 comments
Labels
priority: must-have Features that must be done before we can deploy. q4 These are things that we want to do during q4

Comments

@p-offtermatt
Copy link
Member

p-offtermatt commented Oct 16, 2024

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.

@p-offtermatt p-offtermatt added v2 q4 These are things that we want to do during q4 priority: must-have Features that must be done before we can deploy. and removed v2 labels Oct 16, 2024
@p-offtermatt
Copy link
Member Author

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.
I think this is not very hard technically; the main problem is defining the structure we want, what powers should lie with the committee and what should be with the Hydro voters/the Hydro DAO. I think this fully allows us to implement the hATOM governance idea from the litepaper pretty easily though

@p-offtermatt
Copy link
Member Author

initially the hydro governance should just be used for 1-off props like:

  • should we elect this committee member?
  • should we remove this committee number?
  • should we increase the locking caps?
  • deciding on the rev share between cp & hydro lockers
  • authorizing a tiny of portion of POL yield to be used to compensate hydro committee members for their work

@p-offtermatt
Copy link
Member Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: must-have Features that must be done before we can deploy. q4 These are things that we want to do during q4
Projects
None yet
Development

No branches or pull requests

1 participant