[bisq-network/roles] Mediator (#83)

[huey735]

| Reason  | Cycle 20  |
|---|---|
| BANK_PROBLEMS  | 14  |
| BUG  | 38  |
| OPTION_TRADE  | 0 |
| OTHER  | 9  |
| PEER_WAS_LATE  | 8  |
| SELLER_NOT_RESPONDING  | 5  |
| TRADE_ALREADY_SETTLED  | 6  |
| USABILITY  | 2  |
| TOTAL  |  82  |

Sorry for being late on this report. The above are for tickets opened since my last report -November 19th - till the end of the Cycle 19's end of deadline for compensation requests - December 27th.

@chimp1984 I'll break down the distribution of the 38 bugs in Cycle 19 bellow, but from my experience in these last weeks ( with the new releases) is that the main bugs are:
- funds showing as locked when the trade failed - SPV resync doesn't always fix this
- Bisq not recognizing that Deposit tx has been confirmed
- BTC seller being unable to confirm that they've received the payment

Here's the breakdown for tickets opened between Nov 19th and Dec 27th that were assigned the BUG label:
11 - Trader's Bisq client showed the Deposit tx as unconfirmed despite the opposite being true.
10 - BTC Seller wasn't able to confirm the receipt of funds despite the BTC buyer having clicked "Payment Started".
4 - Trader's Bisq client showed the Deposit tx as unconfirmed despite the opposite being true.
3 - The Deposit and Payout transactions weren't properly constructed.
3 - The Taker fee and Deposit transactions weren't properly broadcast.
3 - Trader's Bisq client showed the trade as failed despite the opposite being true.
1 - Needed to update Bisq in order to finish the trade. Not necessarily a bug.

-- 
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/83#issuecomment-754862703
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210105/7d177c17/attachment.htm>