-
Notifications
You must be signed in to change notification settings - Fork 139
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
Voting module aggregator #803
Comments
Closed
original spec from @Callum-A: https://gist.github.com/Callum-A/53319b415246a89cade7e656fc8ff01d |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
DAOs may want to derive voting power from multiple different sources. Maybe they want both token and NFT governance tokens, or consistent members and fluid token membership, or two different token types. All of these should be possible.
To accomplish this, we need to create a voting module that allows for the registration of other voting modules—essentially a voting module aggregator. This is similar to Neutron's voting registry.
The DAO needs to be able to register a set of voting modules on creation, as well as be able to add and remove existing voting modules. All voting modules should be removable except when there is only one remaining.
Additionally, each voting module should have a weight so that voting modules can be equal or weighted differently. This configuration should be updatable. Weights should be able to be set to 0 so that voting modules can be disabled.
We must validate that at least one voting module has non-zero weight on creation, when updating any weights, and when removing any voting modules.
The text was updated successfully, but these errors were encountered: