[bisq-network/support] Reimbursement request for trade MZEFILM (#500)

Bisq-knight notifications at github.com
Sat Sep 26 14:38:03 UTC 2020


yes, @invertedbobb let's keep the two things separate.

1) **your compensation** -> I read from [here](https://github.com/bisq-network/support/issues/502#issuecomment-699031864) that you agree with what we proposed. Good, we can close this part of the topic then. 👍

2) **precedence and what we should do about cases like this**. Like I said in the other message, @invertedbobb is welcome to add his suggestions here and it should not be specific to this case, but a general approach to things. Specifically how do we solve:
* How long from the delayed payout tx is published (and received by the DAO donation address) until we approve (and issue BSQ) a reimbursement by the DAO? how long should that period be? - keep in mind that it needs to take into account at least some time for a trader to contest a reimbursement request on github.
 * How do we account for and mitigate risks taken by the DAO? in this case, there is a risk being taken by the DAO related to the trade that doesn't have a payout tx (thus has +2 BTC locked) and is the case for one of @invertedbobb's transactions. The DAO is trusting that @invertedbobb is 1) not  trading with himself and assuming that 2) the other trader will not be back to sign the mediation suggestion thus signing the transaction. If either of these cases materialize, the DAO issued BSQ that was not accounted for by the donations it has, i.e. all Bisq contributors pay that price with BSQ inflation.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/support/issues/500#issuecomment-699503841
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200926/aa72c3bd/attachment.html>


More information about the bisq-github mailing list