Open plaidfinch opened 1 year ago
We're in a good position to close out the next ~3-4 items on the checklist via https://github.com/penumbra-zone/penumbra/pull/1881; but higher priority currently on unblocking Zpoken work, so this work might slip to a subsequent sprint.
This has some subtasks that aren't marked V1, should they be?
A governance MVP consists of:
Penumbra proposals are controlled by a client-side state machine which burns and mints NFTs corresponding to the state of a proposal. There is no
NoWithVeto
vote, unlike in the Cosmos SDK; instead, there is a threshold ofNo
votes (out of all total votes cast) which causes the proposal to be vetoed. This diagram shows the flow of a proposal from start to finish:In the above, rounded grey boxes are actions submitted by the proposal author, rectangular colored boxes are the state of the proposal on chain, colored circles are outcomes of voting.
Completing governance is broken down into the following sequence of remaining work:
Initial cleanup
Refactoring and changing current functionality
Delegator voting (PR #1881)
Cleanup and finishing tallying (PR #2055)
Validate parameter change proposals
Implement the DAO (PR #2072)
Allow DAO to interact with funding streams (also in PR #2072)
Make chain halts sticky
Supporting DAO interactions
Cleanup and documentation
IBC actions
Testing and assurance
Further enhancements