I am would like to propose a new AstroDAO feature that would make to easier to authorize multiple transfers at a time (e.g., three team members all worked on a project and each gets a different amount) and that could also be used to incentivize people in DAOs to vote.
I started out with the thought that I would like to build incentives to vote into my DAO, and then realized that a more general functionality would be useful as well.
The problem is a lot of people don’t vote in DAOs.
The solution could be a simple and automated way to reward people for voting. The DAO can set up a pool of tokens or NFTs for a specific period that will distributed at the end of the period among the people who vote based on their votes. The distribution could be based on relative quantity of votes, but it could also take into account other factors such as how quickly someone votes or conviction (how long their vote is in place).
If we were to add this functionality, we should also be able to enable a proposal to make multiple transfers at a time. In the ideal world, you can add as many simultaneous transfers as needed to a proposal.
So in summary, I am suggesting two new proposal capabilites:
Proposal specifies a reward pool for a specific period (e.g., the month of June). The reward pool could be static (e.g., 100 NEAR) or dynamic (e.g., X NEAR per proposal voted on during the period). Proposal also specifies the allocation method. Basic allocation method would be relative number of votes. Alternative methods could take into consideration other desired actions (e.g., how quickly they vote relative to other voters on specific proposals). At the end of the period, AstroDAO would (automatically if possible) calculate the allocations and make the transfers. I think it would be cool if the data was posted in a comment on the proposal as well.
Since we are making transfers to multiple people if we do #1, we can abstract out that to create a multiple payment functionality. Proposal specifies description of why payments are being made, and two more transfers (i.e., near address and amount). User can add as many transfers as needed in same proposal. This could potentially be implemented by adding the capability to add an addition transfer to existing transfer functionality.
If that all makes sense…