Replies: 3 comments 5 replies
-
Agreed Requires our Chrome Extension to inject a custom UI element on GitHub. Possible but backlogged. Not sure how an escrow can be done on chain in a gas efficient manner (particularly for small bounties.) Perhaps there is a more viable architecture here @rndquu We have discussed the concept of "secured credit lines" aka insurance in the research meeting last week, in this topic, but deemed that it's not a good idea to get into insurance. We don't want to custody partner funds in order to limit our own liabilities. @Draeieg if you have more color to add on this topic from our conversation please share. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
We can simply restrict bounty hunters from getting assigned to an issue if there are not enough funds in the bot's wallet address to cover the bounty payment. Example:
|
Beta Was this translation helpful? Give feedback.
-
Here is the situation I encountered:
Worked on a bounty. finished. went to claim and get an error message. The bounty master's wallet had insufficient funds.
big problem that should be exorcised.
one thing a bounty hunter should not worry about is getting paid on DevPool. Two thoughts on this:
2.1 once a bounty master opens an issue the funds for the task are deducted from the balance and earmarked to the bounty (an escrow). this cannot be removed or cancelled once a bounty hunter locks in the task.
OR
if we want the transaction to go from master to hunter directly, establishing "secured credit lines" for each bounty master by which they deposit a % to devpool, which they cannot exceed, for their projects until we see they are not going to rug. OR to avoid a long term mega rug- limit the number of open bounties and $ amounts.
Beta Was this translation helpful? Give feedback.
All reactions