[bisq-network/support] Reimbursement for trade u3rv0j (#512)

[Bisq-knight]

He provided logs, but they only go as far as the 2nd of October.

To clarify: the trader contacted me some time after he tried to initiate mediation (he attempted mediation on Aug 20th, contacted me on 6th of September) and we tried multiple ways to fix the situation at that time to no avail. He contacted me again on October 8th, which is when we started discussing the problem again. 

>From the long hiatus I honestly thought he had solved it with his peer, which is not unprecedented and thus the trade never actually would've shown in mediation. This part I believe is my fault in not following up on my keybase messages and not requesting for logs upfront.

This is the view of my mediator dashboard when searching for his trade:
![image](https://user-images.githubusercontent.com/60526727/97276861-a96db180-182f-11eb-9e61-096d489ad7d5.png)


**To summarize we have to decide whether or not to issue a reimbursement of 364 BSQ in light of:**
* A bug without logs
* a trade with an unfunded donation

We can ask the trader to continue trading in the hopes of running into the same problem again and then collect the complete logs. 

Based on his suggestions:

> * Fix bug of mediators not being able to see trades they are assigned to.

We don't have information to investigate this further. The only way is to try and repeat the problem, or be vigilant about other traders who might be in the same situation
> * Fix dumping the delayed payout transactions not working.

I think that has been solved with the latest release as it was a known problem and time has been spent on it
> * Ensure users get a timely response from support.

You had a specially different experience here as your messages did not reach support, but I'd say that whenever you reached out on Keybase the responses were timely
> * Fix Trojan warnings from MalwareBytes on Bisq’s website.

I don't know how we can fix this but seems unrelated to this trade in particular.




-- 
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/512#issuecomment-717109365
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20201027/d23b8074/attachment.html>