IPFS Microgrant + per-project payouts #186
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kredits/contracts#186
Reference in New Issue
Block a user
Maybe we could apply for one of these for the upcoming IPFS work: https://github.com/ipfs/devgrants/blob/master/MICROGRANTS.md
A general question/problem, which came up a few times already, is how we can reward contributions to specific parts of the project, e.g. only Kredits or only Chat, or in this case only IPFS-related work.
I just had a quick thought: what if, instead of payouts per project, it works the other way around? As in, the dividend payout would draw from project-specific vaults, according to how much was done for that project? This way, you could still work on anything you want, but if too much work would be done on things that there's no budget for, then everybody would earn less. Thus giving contributors an incentive to get the right vaults filled for things they deem important, while donors/customers can meaningfully signal their preferences and priorities as well.
I like the general idea!
I am just a bit concerned about the complexity to implement it and would first want to have the reimbursements and a normal vault running. :)
Yes, the comment is not about planning priorities, and is completely separate of reimbursements. It is purely about the design of contributor dividends.
Let's try to imagine how it could actually work, without being scared of implementation details during what is still brainstorming phase for dividends. ;)
... also, the same as for reimbursements still applies: we can try the concepts with zero contract implementation first, to validate it and see what the implementation would actually require.