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

[Chris Beams]

## 2018.10 report

I arbitrated 68 disputes this month, and as @ManfredKarrer reported at https://github.com/bisq-network/proposals/issues/52#issuecomment-433663600, quite a few are due to bugs / networking issues. The most common ones this month are dropped trade protocol messages between buyer and seller, where the seller doesn't know the buyer has initiated payment because the 'Payment Started' message never gets to the seller, or the seller's 'Payment Received' message never makes it to the buyer's client. These issues are happening even though the affected clients report that the message was 'received by peer'. In any case, these all end up in arbitration, and as Manfred reported, they are responsible for something like 40% of all cases.

On the bright side, it's good to see that the number of disputes has not gone up linearly with the number of trades during this recent volume spike. 68 is certainly more than I usually do in a month, but only by 10 or 20, i.e. a 25% or so increase. That's pretty good considering that we doubled the number of trades we usually do this month (2000 vs 1000). Much of this can be attributed to the fact that most of this month's volume increase was Monero-related, and that Monero users are generally more sophisticated and less likely to end up with disputes, but it doesn't explain why we wouldn't see 2x as many bug-related disputes.

In any case, getting somebody to work on these dropped message bugs is important.

/cc bisq-network/compensation#160

-- 
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-434772915
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20181031/873da604/attachment.html>