-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Description
Currently the way AlloKit works is that each Round / Pool has a voting token and a rewards token.
This makes it flexible to create a wide range of pool strategies. For example, the RetroFunding and QudraticFunding can have the same logic (only different allocationToken) but this simplicity comes with some tradeoffs:
- The Badgeholder votes are described as ERC20 tokens thus the votes are public (are private erc20 an option?)
- It requires an ERC20 to be deployed before creating the Round / Pool (could be a dialog in the create pool component)
The alternative is to store the voters and votes in a private db but that complicates the implementation because RF and QF will have different function calls and storage.
Metadata
Metadata
Assignees
Labels
No labels