[bisq-network/roles] Arbitrator (#13)

[Chris Beams]

## 2018.05 report

I arbitrated 46 cases this month.

Major issues continue to be:

 - dropped "Payment Started" trade protocol messages (bisq-network/support#84)
 - dropped arbitration chat messages (bisq-network/support#85)

Another issue I haven't brought up before is the problem of traders sending arbitration messages _after_ I've closed their ticket. When this happens, I never see the additional messages, because the ticket is hidden away from me, and because no sort of notification occurs when closed tickets get new messages.

Trade `NX5C4W5F` was such a case, and it left the buyer very worried for nearly a month. The buyer's bitcoin had never been released to them, even though I closed the arbitration ticket in their favor. The payout transaction never occurred, and I believe this is because my close ticket message / payout transaction signing message never made it to the buyer's client in the first place. I believe it's for this reason as well that the buyer was able to continue messaging me: their client never got the signal from mine that the conversation was over. Note that also have reason to believe, from the content of his comments, that he never received _any_ of my arbitration messages.

So this specific problem can probably be generalized to the known problem of dropped arbitration messages. We may be able to mitigate the effects effects of this specific problem, though, without necessarily having to fix the general problem. Getting any kind of notification that a closed message is still active would be helpful, but that's probably a lot of code we wouldn't otherwise want.

@ManfredKarrer has been thinking about doing "read receipt"-style messages as a way of solving the dropped message problem, i.e. getting an explicit confirmation message from your peer that they definitely got your message, with, say, a hash of its contents to prove it. We could build on this approach to ensure that my arbitration ticket doesn't actually close until we've gotten confirmation from the peer's side that their side is closed as well.

In any case, this problem creates a nasty experience for users, so would be good to remedy / mitigate in some fashion asap.

(I'll create a dedicated issue for the above new issue shortly)

/cc bisq-network/compensation#74

-- 
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/roles/issues/13#issuecomment-393193780
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180530/decfdbeb/attachment-0002.html>