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

[Bisq-knight]

In this trade I got the following:
Both parties replied my messages, here's a summary based on the timestamps in my bisq client

* 25th of Aug - trade started 
* 30th of Aug - Buyer says Seller is not responding (did not provide proof of payment). I suggested to wait
* 4th of Sept - The Seller said this trade went into Failed on his end and didn't answer anything else
* 5th of Sept - The delayed payout tx was [published](https://blockstream.info/tx/90a378116186789b458606d13fc41b110de008040a8cad90c0d14003c05174c0) (I don't know by whom, as the mediation had not been issued by then) 
* 7th of Sept - Seller asks me where is his part of the trade is


So I don't think this is total unresponsiveness, but it was a delay on the Seller side as he started answering but there was not enough time to arrive at a solution. I then, after the delayed payout tx was published, issued a simple amicable mediation as it was already out of my hands and wanted to close the case.

I side with Wiz that the Buyer does deserve compensation, as he put this case up for us to discuss while the Seller simply didn't show up after the messages above. But I don't think his compensation should be total amount. We don't have precedent of the DAO holding funds in case if a trader shows up in a month but this case shows us that:
* Unresponsive traders can happen in all stages of the trade: during the trade, during mediation, during arbitration -> what should be our policy on that
* How, exactly, should traders be compensated for taking the time, effort and fx risk of going through the reimbursement process to get their share in BSQ?

-- 
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-698298672
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200924/1274f5a3/attachment.html>