ManfredKarrer
commented
5 years ago I close it for now as it is not used atm. Can be re-opened once it becomes active.
Open ManfredKarrer opened 5 years ago
ManfredKarrer
commented
5 years ago I close it for now as it is not used atm. Can be re-opened once it becomes active.
m52go
commented
5 years ago Re-opening this issue, as it's the one we need to use, since it's in the code.
bisquser
commented
4 years ago Cycle 9: I have mediated 65 cases and I have 9 cases pending in this cycle. I will make a breakdown of the cases in the coming days.
Cycle 8: I am a mediator and have a bond of 10 000 BSQ locked up. I have so far mediated 104 cases and have 8 cases pending. The cases started October 29. I don't know how I can prove this but I will discuss with the developers if a way can be found. For now it will be necessary to trust me. If I cheat I risk that my bond being confiscated. I will publish a report in a few days with a link here including a summary of the disputes.
In 16% of the cases the transactions was not published, but this problem has essentially disappeared with version 1.2.4 In 42% of the cases the seller released the BTC without further ado, often after a late payment. In 6% of the cases the buyer did not pay and stopped responding. In 5% of the cases the seller stopped responding and did not release the BTC despite being paid. In 8% of the cases the banks caused trouble, in a few cases due to "suspicious activity". In 2% of the cases the confirmation button of the seller did not work. These cases occurred in v1.2.3
The non-responding traders will likely not sign the mediators suggestion and are thus expensive for the DAO. If (when) the volatility goes up there will be many more forward trades and non-responsive buyers. If there was a way for disputes where the seller releases the BTC to simply go away it would help the mediators. I have a feeling that the number of disputes are decreasing as the traders move to v1.2.4.
chimp1984
commented
4 years ago I just looked up quickly the rough number of trades in that period and it was about 3000 trades. So if the other mediator has similar numbers we have about 210 disputes at 3000 trades which is 7%. This seems to be a bit above the average what I remember from the past (5%) but as we had several issues over the past weeks and as with the new trade protocol some cases are caused from usability/confusion this seems to be in the expected range. We have to work hard to bring those number down so user experience gets improved and costs for the DAO decreased.
leo816
commented
4 years ago I have done 165 mediations so far.
this overview was made 20 days ago:
an overview would be: -failed tx (not published) 35% -seller not responding 20%(usually they eventually respond and end up releasing) -bugs (like not being able to click on payment received or stuck on the blockchain confirmation part even though the tx has confirmations) 15% -banking issues 10% -people not wanting to complete the trade for various reasons 5% -users want to get their account signed 5% -Buyer used a different bank account to make the payment 10%
*the message issues have been completely solved, I believe all my messages have gone through and haven't been aware of lost messages from other parties.
*the invalid tx not getting published problem is also much better now but its still the biggest problem.
Since I made this overview 20 days ago, invalid transactions have significantly been reduced on my end, and I would say the biggest issue is when the BTC seller can't see the confirm payment received Button.
most recent overview would be:
failed tx (not published) 5% Seller not being able to see the confirm payment button 20% banking issues 10% both parties not wanting to complete the trade for different reasons 10% Buyer used a different name from the one shown on their Bisq account. 15% seller stopped responding and didn't release the btc, almost always ended up making a later payment 40%
ifarnung
commented
4 years ago It should be clear to any observer that the BSQ price and market has been very weak this month so far. Of course it's difficult to balance the supply and demand, and only 6 months ago I could barely find any BSQ to buy for my personal trading. But issuance has soared since then relative to the amount being burned in fees at least. So it does makes sense to me to look closely at the operating costs that we are seeing in compensation requests. Maybe there are places to cut costs.
Not that I can say I understand the work required to mediate a case, except from the point of view of a customer in a mediation, but it struck me that 50 BSQ per case was quite a high rate to charge. Now we are seeing the monthly bills hitting in comp. requests and I can give some minor analysis.
Hypothetical User X (prefers to remain anonymous) made 225 trades and had 9 cases that went to mediation (or legacy arbitration), none due to negligence, though 1 or 2 to software errors the prevented the trade from completing.
A mediation rate of 4% and a cost to BISQ of 450 BSQ. Fees paid in BSQ and revenue to BISQ were 3,050,000 sats all on the maker side. So assume 3x for the taker side, 9,150,000, arriving at 12,200,000 sats total. At 8500 sats per BSQ this is 1,435 BSQ.
So in an average case, the cost of mediation alone is already a huge chunk of fee revenue. And because it's a variable cost, it will scale more or less with exchange volume growth. So I think it's quite important to carefully consider the cost of that role.
leo816
commented
4 years ago Mediations are less and less every cycle, with our feedback programers are dealing with the different bugs that are appearing. I believe our role to be critical but also fading. The end goal is to have no mediation. @ifarnung rnung I believe your analysis not to be precise to the fact that you are simply putting out a single case from a trader and using it as the norm. The vast majority of users never have any issues, and the ones that do are every month less and also helped by us the mediators through keybase, please keep in mind that this rate also considers this kind of support and is not asked for anywhere else.
chimp1984
commented
4 years ago @ifarnung Thanks a lot for your analysis! You arre absolutely right we need to get mediation (and even more refund agent) cases down. They are a major cost factor (also with legacy arbitration). To fix open bugs, improve UX and finetune parameters like security deposit to bring that down is essential. Once bugs are fixed we should also start to extend the mediators group but onboarding mediators is still quite a bit of an effort and I think we should rather invest that effort in improvements to reduce cases before extending mediators.
To help to get there we need more detailed reports and better communication from mediators/refund agent to developers.
leo816
commented
4 years ago Cycle 11 I have mediated 313 cases since I started as a Mediator, On the previous cycle the biggest issue we faced was the bug that had to do with the seller not being able to confirm that he had received the payment, even though the buyer had clicked on "payment made" correctly. On this cycle the main concern relies on the seller not confirming the mediation ticket proposal. Knowing they will lose the deposit, they still disappear after they've received the fiat/altcoin payment from the btc buyer. This does not have an obvious solution but we are currently working on the support team to solve this as soon as possible.
an overview of the reasons why the tickets were opened in the first place would be:
-Failed tx: 20% -Seller makes a late confirmation: 20% -Seller never answers: 10% -Banking issues: 25% -User's not having the correct information or using the wrong bank account to make the payment:10% -seller not being able to confirm the payment was made: 10% -Both parties agree to cancel because a mistake was made: 5%
Notice the issue regarding the Sellers not being able to confirm still stands (although significantly reduced) but that is because there have been some cases where users that have opened the dispute had to wait 24hrs for the refresh button to appear so decided to open an early dispute and solve the problem faster. that waiting time will be cut down on future updates.
Invalid txs have been considerable this cycle although the number has not increased dramatically as you might think from comparing from last evaluations, I believe on the previous assessment I was only referring to the later part of the cycle and hence wasn't an accurate representation.
ifarnung
commented
4 years ago 313 cases this cycle is a HUGE amount of cases and exactly the worry I was highlighting a few months ago about the very high costs of Mediation based on this roles compensation of 50 BSQ per case. I'm sure that you are providing excellent resolution of all these errors and failed trades, but can the DAO afford to pay 15,000+ BSQ this cycle for your support efforts? It just doesn't seem proportional at all to the amount of work done. In my country, 50 BSQ is almost a day's wage for white collar work, so we must admit this isn't a year's worth of work in one cycle... I understand that the first mediator set the bar at 50 per case, and you were just following, and I am sure some discussions have been had on how to budget this expense with the new Team Lead system. Anyway, often silence on BISQ means consent once it comes time to vote so I will voice my objection early so that at least people can think over how it should be handled going forward.
cbeams
commented
4 years ago 313 cases this cycle is a HUGE amount of cases
This is a misunderstanding; 313 is the total number of cases @leo816 has mediated since he has been a mediator. From his report for cycle 11 at https://github.com/bisq-network/compensation/issues/495#issue-564822991:
I have mediated 313 finished cases so far. [...] 61 on February 22 on March so far
(@leo816, it would be better to do everything in terms of cycles, not months, but that's a nit)
50 BSQ [per case is too much ...]
Also as mentioned in @leo816's cycle report, he is requesting 4100 BSQ based on the 50 BSQ per case figure, because this was the agreed upon figure when we decided to split up his compensation request in cycle 10 over two cycles. Going forward, he will request compensation at the rate of 25 BSQ per case:
As discussed with @cbeams this is the last cycle using 50 BSQ/ case [...] From the next cycle onwards, the price used for compensation per case will be cut in half to 25 BSQ.
And actually, I want to make a correction to that understanding Leo and I established. As discussed in @ifarnung's own proposal to become a mediator at bisq-network/proposals#184, we should not be denominating the value of work performed in BSQ. It should always be denominated in USD and then converted to BSQ at the published 90-day moving average for the current cycle. So, leo, if we do that rough calculation, you've been receiving 50 BSQ / case during a period where the 90-day average has been around 0.66 USD/BSQ. That equals 33 USD per case. Adjusting this down by half 50/2 = 25 BSQ per case, we get 33 USD/2 = 12.5 USD per case. @ifarnung is requesting 1000 USD/cycle in his proposal to become a mediator, and that would be the equivalent of 80 cases, which is higher than the current average number of cases per mediator (with 2 active mediators). From a budget perspective, I am fine with the agreed-upon 12.5 USD / case, and I would also be fine with a fixed amount per month as @ifarnung is suggesting. Assuming that @ifarnung's proposal gets approved and we go with 1,000 per month there, I'd let you choose, @leo816, whether you'd like to agree to the same. There is a lot of value in having competent mediators at the ready regardless of how many cases are coming in, and I believe that paying a steady rate for that is probably a better approach than paying per-case.
In any case, these changes were made in part because of your feedback, @ifarnung, so thank you for that. Note that the other mediator, @bisquser, is revoking their key, and so there won't be any contention about the 50 BSQ / case figure there. So we're basically dealing with a fresh start now.
cbeams
commented
4 years ago I've updated the description of this issue to link to the new https://bisq.wiki/Mediator role documentation that @leo816 has been putting together in bisq-network/admin#26.
ifarnung
commented
4 years ago Sorry for my several misunderstandings, yes the 313 number being many months of work makes much more sense. Just to be clear, I am not asking to become a mediator, I'm far from skilled or capable from the providing that service. So once again, my thanks to @leo816 and @bisquser for the excellent and skilled work they performed in that regard. My critique was only the overall budget expenditure for a scaling and ongoing cost. Agreeing to a 50% cut in pay is certainly a show of good will, helpful participation in the austerity measures, and is very much appreciated by the community I am certain. So thanks to all for working that out. And at the lower rate per case, and with a lower estimate of cases handled per cycle, I think it does make more sense to compensate as you guys have agreed. Thanks for the update, another confidence boosting message to stakeholders. :)
cbeams
commented
4 years ago Just to be clear, I am not asking to become a mediator
Ugh, my bad. I thought that was your proposal and see now that it is @wiz's. In any case, my comments based on it still stand, but thanks for clarifying, @ifarnung.
leo816
commented
4 years ago we get 33 USD/2 = 12.5 USD per case.
should be 16.5 no? which means that 60 cases would be around that 1000$ mark, sounds about right. I have no problem with changing to a steady rate but my question now would be, how do I value all the 149/313 mediation cases (+ all the cases in between now and the next cycle) that I haven't gotten compensation for yet? Im guessing that it would fall under the 25 BSQ/16.5 USD agreement we made. I think is best if I continue with the 16.5 USD until I catch up at least, but im open to discussion.
cbeams
commented
4 years ago Hah, that was a terrible calculation on my part, thanks for catching it.
On Mar 12, 2020, at 7:12 PM, leo816 notifications@github.com wrote:
we get 33 USD/2 = 12.5 USD per case.
should be 16.5 no? which means that 60 cases would be around that 1000$ mark, sounds about right. I have no problem with changing to a steady rate but my question now would be, how do I value all the 149/313 mediation cases (+ all the cases in between now and the next cycle) that I haven't gotten compensation for yet? Im guessing that it would fall under the 25 BSQ/16.5 USD agreement we made. I think is best if I continue with the 16.5 USD until I catch up at least, but im open to discussion.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
bisquser
commented
4 years ago Cycle 10-11: I have mediated 206 cases and I have 12 cases pending in the two last cycles. I have now revoked my role and will be replaced by different mediators, if the DAO so choses.
leo816
commented
4 years ago Cycle 11-12: 142 cases were mediated on March, that is double the monthly average due to the fact that the other mediator stepped down mid-cycle I was left with double the cases.
-this is an overview of the monthly cases up until now:
16 cases from the old mediation. 83 cases in November 62 on December 69 on January 61 on February 142 on March 38 on April so far
On the last cycle I mentioned that the main concern relied on the seller not confirming the mediation ticket proposal, knowing (or perhaps not fully knowing in most cases) they would lose their deposit, even then, they would still disappear after they received the fiat/altcoin payment from the btc buyer. This issue is still happening on this cycle and it does not have an obvious solution but we are currently working with the entire support team to solve this as soon as possible, specially given that we faced an attack and it passed as undetected for a week as a result of it being a recurring issue within the daily mediations.
Similarly, the main problem when talking about user-experience is that the seller can even confirm the payment after 9 days and would still get his funds without any penalty. That can't be the norm for a trader who is using the app correctly and is still being penalized. There has also been an increase in cancelled trades due to banks cancelling payments, specially with belle payments, there have been a lot of issues.
The new fixed rate of 1000 USD for the mediation role is done to ensure the mediator's interests are aligned with Bisq's. Before the 11th Cycle the price used for compensation per case was cut in half to 16.5 USD . Out of the 313 cases I had closed until then, only 162 were accounted for, corresponding to 2 cycles respectively, that leaves 151 cases unaccounted for or the equivalent of 2 cycles worth of cases. In the per-case scenario, that would amount to 2491,5 USD. Even though that would be the right price agreed upon for that time period, I believe that given the recent events on Bisq, its best to account it as just two cycles with the new fixed system, so that would equate to 2000 USD. The compensation for this cycle would then would be:
Bisq-knight
commented
4 years ago I'm still getting my head around on what is most relevant to report here.
Overview:
Notable pattern: most cases actually are a result of fat fingers. Traders delay their payments or call mediation prematurely. The same people usually end up solving their own problems. I'm gonna gather some more data on that for the next reports.
wiz
commented
4 years ago Handled 94 mediator tickets for 47 trades, only a few currently open pending nonresponsive trade partners waiting to begin arbitration
Bisq-knight
commented
4 years ago Summary:
Total Cases in Cycle: 23
Still open: 4
Closed: 19Total amount mediated: 2.75 BTC in trade amount (excluding deposits) Avg. case size: 0.12 BTC (average affected by a couple of large cases, most cases are 0.01 BTC) Avg cost per case: 43.88 USD
Avg. Buyer account age (for fiat trades, and trades up to 0.01 BTC) (21 trades, 58% of all cases)
| Buyer median age | Seller median age | |
|---|---|---|
| Cycle 12 | 17 | 38 |
| Cycle 13 | 22 | 62 |
| The same view for trades above 0.01 (15 trades) | Buyer median age | Seller median age | |
|---|---|---|---|
| Cycle 12 | 99 | 402 | |
| Cycle 13 | 114.5 | 133.5 |
20 USD per case or 1000 USD per month, whichever is lower. 20 because it is significantly cheaper for the DAO (at least from my standpoint) and still compensates mediators for the time spent troubleshooting users yet keeps capacity available for when volume demands it without having the lead time to propose a role, do the bonding and onboard/train mediators when needed.cbeams
commented
4 years ago @Bisq-knight, is the 402 value for seller median age a typo?
Bisq-knight
commented
4 years ago @Bisq-knight, is the 402 value for seller median age a typo?
Nope, is actually the value that divides the larger fiat trades in the last cycle: This is the array of ages for this cohort: [18, 45, 226, 402, 527, 532, 789]
leo816
commented
4 years ago Cycle 13 report
Total Cases in Cycle: 48
Still open: 9
Closed: 39
- Most cases are caused by new users (most likely buyers). If we increase efforts in education we may be able to reduce mediation requests. (see tables above)
I agree completely with this point but I believe the solution is to have a "most asked questions" bullet point list filled with the most common issues new users face and have that as a way to avoid some of the pointless mediations we are seeing.
Steve Jain suggested that I change my language to Spanish, Once I change my data directory I will also add Spanish as a language, In case I can only chose one language then might be interesting to have one of the mediators who can speak this language, giving that option to users who might find it easier to communicate in their native language.
On my case the most common issue I see is still one of the parties not responding, usually the seller.
A big issue we still haven't taken measures over is the fact that a buyer is able to wait 10 days to make a payment and he will receive no penalty, similarly a seller can wait many days before releasing the btc an as long as the funds don't get to the donation address he will receive his funds like nothing happened. Whenever this happens this makes it a huge impact on the user who is obviously frustrated and has been penalized with time when they did nothing wrong.
wiz
commented
4 years ago Bisq-knight
commented
4 years ago Summary:
Total Cases in Cycle: 30
Still open: 7
Closed: 23With that in mind here is the consolidated view on Cycle 13 and the WIP for Cycle 14:
Cycle 13 [Consolidated]
Total Cases in Cycle: 36
Amount mediated: 3.4068 BTC
Notes: what I wrote beforeCycle 14 [WIP]
Total Cases in Cycle: 30
Amount mediated: 2.7203 BTC
Notes: we had quite a few +6 cases related to Revolut. This was mainly due to Revolut updating their design and breaking the flow that bisq traders would normally do. Now the solution is very simple: ask the trader for the username and search with that, also, keep in mind that usernames ARE case sensitiveTotal Cases in this Cycle: 38
Still open: 10
Closed: 28Because we need to do these reports in the middle of the voting period I think it is worth to just update the reports once the next report is done.
I agree with this proposal and I will analyze the cycle up until today, will update it at the end of such cycle with the remaining information.
35% Banking issues (Revolut, Zelle, SEPA)
15% both parties agreed to cancel
35% BTC seller took longer to answer/make the payment
15% Unexperience, parties unsure of how the process works
This cycle we've had a considerable amount of issues with Revolut between @Bisq-knight and me, the problem relies on revolut not recognizing some of the phone numbers as having accounts on the platform. Usually the accounts are fairly new. The solution we've suggesting is creating a payment link/ using the username (@example) or if none of these work just making a normal transfer using the IBAN revolution provides.
Another pending issue is the problem with users who never respond and trades end up going to arbitration which makes no sense for the other party that often has done everything correctly. Similarly a BTC seller may release the funds after 10 days with no penalty at all, there must be some way to control this.
wiz
commented
4 years ago leo816
commented
4 years ago Total Cases in this Cycle: 23
Still open: 6
Closed: 17New action protocol was proposed.
I will analyze the cycle up until today, will update it at the end of such cycle with the remaining information.
This cycle I've had nearly no banking issues in comparison with cycle 14. Specially with Zelle and Revolut where we've had most problems lately. I've had an issue with a user that could not click on "payment started" button. Users have seemed to have learnt to solve the Revolut issue by creating a payment link/ using the username (@example) or just making a normal transfer using the IBAN revolution provides.
A clear take away from this is that most mediation tickets arise from users being impatient, they seem unnecessary and we will keep a close look into the following cycles to see if this trend continues.
Another pending issue is the problem with users who never respond and trades end up going to arbitration which makes no sense for the other party that often has done everything correctly. Similarly, a BTC seller may release the funds after 10 days with no penalty at all, there must be some way to control this. (still working on this)
Bisq-knight
commented
4 years ago Total Cases (so far):
Open cases: 4 (2 from cycle 14 and 2 from cycle 15)
Closed: 20
Amount mediated: 0.9389 BTC I'll write up the summary and analysis once the cycle is closed
wiz
commented
4 years ago leo816
commented
4 years ago Total Cases in this Cycle: 29
Still open: 6
Closed: 23I will analyze the cycle up until today, will update it at the end of such cycle with the remaining information.
Users are now starting to accept giving the Revolut username when making a transfer and that is speeding up things.
There have been some discussions between mediators as to whether we should standardize certain behavior patterns from users. For example when the buyer doesn't want to continue with the trade and refuses to make the payment. We are leaving this penalty % for the mediator to estimate. In the future I would like to see and fixed rate with maybe a last verdict from the mediator, but I think having things standardized makes it easier for the most part.
Another pending issue is the problem with users who never respond and trades that end up going to arbitration which makes no sense for the other party that often has done everything correctly. Similarly, a BTC seller may release the funds after 10 days with no penalty at all, there must be some way to control this. (still working on this)
Bisq-knight
commented
4 years ago Summary:
Total Cases in Cycle: 38
Still open: 10 (6 of which are unresponsive traders)
Closed: 28I had some downtime in the last week of the cycle as I was travelling and connectivity was really bad. I informed of those outages in the #support channel.
Case-wise there were no particular patterns except a few notable things:
wiz
commented
4 years ago Nothing interesting to report.
Total Cases in Cycle: 44
Closed: 39
Open: 5Dispute nr. 163
Opening date: Jul 24, 2020 1:31:05 PM
Close date: Aug 1, 2020 10:24:59 PM
Duration: 8 days, 8 hours, 53 minutes
Summary notes: Parties completed trade normally
Reason: OTHER
Dispute nr. 164
Opening date: Jul 24, 2020 4:52:56 PM
Close date: Aug 8, 2020 12:05:54 AM
Duration: 14 days, 7 hours, 12 minutes
Summary notes: Parties completed trade normally after USPS delay
Reason: OTHER
Dispute nr. 165
Opening date: Jul 25, 2020 4:48:16 PM
Close date: Aug 2, 2020 11:10:23 PM
Duration: 8 days, 6 hours, 22 minutes
Summary notes: Parties agreed to cancel
Reason: OTHER
Dispute nr. 166
Opening date: Jul 25, 2020 7:14:24 PM
Close date: Aug 2, 2020 11:10:59 PM
Duration: 8 days, 3 hours, 56 minutes
Summary notes: Parties completed trade normally
Reason: OTHER
Dispute nr. 167
Opening date: Jul 26, 2020 12:41:23 PM
Close date: Aug 19, 2020 11:48:28 AM
Duration: 23 days, 23 hours, 7 minutes
Summary notes: Seller is unresponsive, buyer provided proof of payment
Reason: NO_REPLY
Dispute nr. 168
Opening date: Jul 27, 2020 7:56:21 PM
Close date: Aug 23, 2020 9:39:53 AM
Duration: 26 days, 13 hours, 43 minutes
Summary notes: Seller confirms payment from Buyer, but unable to use in-app button to complete trade. Mediator to perform Manual Payout using private keys provided by both parties.
Reason: BUG
Dispute nr. 169
Opening date: Jul 27, 2020 8:24:41 PM
Close date: Aug 2, 2020 11:17:31 PM
Duration: 6 days, 2 hours, 52 minutes
Summary notes: Buyer unresponsive, Seller can proceed to arbitration 20 days after trade began
Reason: NO_REPLY
Dispute nr. 170
Opening date: Jul 27, 2020 9:06:14 PM
Close date: Jul 28, 2020 2:22:27 AM
Duration: 5 hours, 16 minutes
Summary notes: Parties agreed to cancel trade
Reason: BANK_PROBLEMS
Dispute nr. 171
Opening date: Jul 27, 2020 11:56:27 PM
Close date: Aug 9, 2020 11:15:45 AM
Duration: 12 days, 11 hours, 19 minutes
Summary notes: Parties agreed to cancel
Reason: OTHER
Dispute nr. 172
Opening date: Jul 28, 2020 3:39:55 PM
Close date: Aug 8, 2020 12:05:07 AM
Duration: 10 days, 8 hours, 25 minutes
Summary notes: Buyer did not send payment and did not respond to mediator
Reason: NO_REPLY
Dispute nr. 173
Opening date: Jul 28, 2020 9:22:04 PM
Close date: Aug 2, 2020 11:19:05 PM
Duration: 5 days, 1 hour, 57 minutes
Summary notes: Parties completed trade normally
Reason: OTHER
Dispute nr. 174
Opening date: Jul 29, 2020 5:06:18 PM
Close date: Jul 31, 2020 10:25:19 PM
Duration: 2 days, 5 hours, 19 minutes
Summary notes: Parties completed trade normally
Reason: OTHER
Dispute nr. 175
Opening date: Jul 29, 2020 10:12:07 PM
Close date: Aug 4, 2020 11:08:51 PM
Duration: 6 days, 0 hours, 56 minutes
Summary notes: Parties agreed to cancel
Reason: OTHER
Dispute nr. 176
Opening date: Jul 30, 2020 3:48:15 AM
Close date: Aug 2, 2020 11:36:08 PM
Duration: 3 days, 19 hours, 47 minutes
Summary notes: Parties completed trade normally
Reason: OTHER
Dispute nr. 177
Opening date: Jul 31, 2020 3:14:38 AM
Close date: Aug 2, 2020 11:36:44 PM
Duration: 2 days, 20 hours, 22 minutes
Summary notes: Parties completed trade normally
Reason: OTHER
Dispute nr. 178
Opening date: Jul 31, 2020 5:33:19 AM
Close date: Jul 31, 2020 10:26:08 PM
Duration: 16 hours, 52 minutes
Summary notes: Parties completed trade normally
Reason: OTHER
Dispute nr. 179
Opening date: Aug 2, 2020 4:54:01 AM
Close date: Aug 7, 2020 11:59:30 PM
Duration: 5 days, 19 hours, 5 minutes
Summary notes: Parties completed trade normally
Reason: OTHER
Dispute nr. 180
Opening date: Aug 2, 2020 12:23:37 PM
Close date: Aug 4, 2020 11:09:35 PM
Duration: 2 days, 10 hours, 45 minutes
Summary notes: Parties completed trade normally
Reason: OTHER
Dispute nr. 181
Opening date: Aug 2, 2020 4:20:27 PM
Close date: Aug 7, 2020 11:56:25 PM
Duration: 5 days, 7 hours, 35 minutes
Summary notes: Parties completed trade normally after delay due to buyer forgot to press payment stared button
Reason: OTHER
Dispute nr. 182
Opening date: Aug 3, 2020 5:02:05 AM
Close date: Aug 5, 2020 3:11:18 AM
Duration: 1 day, 22 hours, 9 minutes
Summary notes: Parties completed trade normally
Reason: OTHER
Dispute nr. 183
Opening date: Aug 3, 2020 10:21:37 PM
Close date: Aug 5, 2020 9:40:52 PM
Duration: 1 day, 23 hours, 19 minutes
Summary notes: Parties completed trade normally, but payment method name did not match
Reason: PROTOCOL_VIOLATION
Dispute nr. 184
Opening date: Aug 4, 2020 5:58:01 AM
Close date: Aug 5, 2020 3:13:06 AM
Duration: 21 hours, 15 minutes
Summary notes: Parties completed trade normally
Reason: OTHER
Dispute nr. 185
Opening date: Aug 5, 2020 5:49:34 PM
Close date: Aug 7, 2020 11:55:46 PM
Duration: 2 days, 6 hours, 6 minutes
Summary notes: Parties completed trade normally after mempool delay
Reason: USABILITY
Dispute nr. 186
Opening date: Aug 6, 2020 12:57:53 AM
Close date: Aug 7, 2020 11:53:22 PM
Duration: 1 day, 22 hours, 55 minutes
Summary notes: Failed trade
Reason: USABILITY
Dispute nr. 187
Opening date: Aug 6, 2020 10:44:44 AM
Close date: Aug 7, 2020 11:51:54 PM
Duration: 1 day, 13 hours, 7 minutes
Summary notes: Parties completed trade normally after agreeing to waive bank name mismatch violation
Reason: PROTOCOL_VIOLATION
Dispute nr. 188
Opening date: Aug 7, 2020 7:51:04 AM
Close date: Aug 7, 2020 11:58:49 PM
Duration: 16 hours, 7 minutes
Summary notes: Parties completed trade normally
Reason: OTHER
Dispute nr. 189
Opening date: Aug 7, 2020 6:56:20 PM
Close date: Aug 12, 2020 1:55:52 AM
Duration: 4 days, 6 hours, 59 minutes
Summary notes: Parties completed trade normally
Reason: OTHER
Dispute nr. 190
Opening date: Aug 9, 2020 7:27:47 PM
Close date: Aug 12, 2020 1:55:02 AM
Duration: 2 days, 6 hours, 27 minutes
Summary notes: Parties completed trade normally
Reason: OTHER
Dispute nr. 191
Opening date: Aug 10, 2020 6:38:04 AM
Close date: Aug 11, 2020 1:00:05 AM
Duration: 18 hours, 22 minutes
Summary notes: Failed Trade
Reason: OTHER
Dispute nr. 192
Opening date: Aug 11, 2020 10:53:34 AM
Close date: Aug 14, 2020 4:46:35 AM
Duration: 2 days, 17 hours, 53 minutes
Summary notes: Parties completed trade normally
Reason: OTHER
Dispute nr. 193
Opening date: Aug 11, 2020 10:11:53 PM
Close date: Aug 14, 2020 3:53:54 AM
Duration: 2 days, 5 hours, 42 minutes
Summary notes: Parties completed trade normally
Reason: OTHER
Dispute nr. 194
Opening date: Aug 12, 2020 7:24:25 AM
Close date: Aug 16, 2020 1:55:57 AM
Duration: 3 days, 18 hours, 31 minutes
Summary notes: Parties completed trade normally
Reason: OTHER
Dispute nr. 195
Opening date: Aug 12, 2020 11:22:50 AM
Close date: Aug 14, 2020 3:52:33 AM
Duration: 1 day, 16 hours, 29 minutes
Summary notes: Mediator confirmed payment
Reason: OTHER
Dispute nr. 196
Opening date: Aug 15, 2020 5:04:54 AM
Close date: Aug 17, 2020 8:46:04 AM
Duration: 2 days, 3 hours, 41 minutes
Summary notes: Parties comlpeted trade normally after mempool delay
Reason: OTHER
Dispute nr. 197
Opening date: Aug 16, 2020 4:49:50 AM
Close date: Aug 19, 2020 10:51:58 PM
Duration: 3 days, 18 hours, 2 minutes
Summary notes: Parties agreed to cancel trade
Reason: OTHER
Dispute nr. 198
Opening date: Aug 16, 2020 11:22:14 AM
Close date: Aug 17, 2020 8:44:39 AM
Duration: 21 hours, 22 minutes
Summary notes: Parties completed trade normally
Reason: OTHER
Dispute nr. 199
Opening date: Aug 16, 2020 3:09:40 PM
Close date: Aug 19, 2020 10:51:36 PM
Duration: 3 days, 7 hours, 41 minutes
Summary notes: Parties completed trade normally
Reason: OTHER
Dispute nr. 200
Opening date: Aug 17, 2020 4:20:23 PM
Dispute nr. 201
Opening date: Aug 17, 2020 4:20:59 PM
Dispute nr. 202
Opening date: Aug 18, 2020 10:49:24 PM
Close date: Aug 19, 2020 10:49:58 PM
Duration: 1 day, 0 hours, 0 minutes
Summary notes: Parties completed trade normally
Reason: OTHER
Dispute nr. 203
Opening date: Aug 20, 2020 2:43:40 AM
Dispute nr. 204
Opening date: Aug 20, 2020 10:08:53 AM
Close date: Aug 23, 2020 9:41:03 AM
Duration: 2 days, 23 hours, 32 minutes
Summary notes: Parties completed trade normally
Reason: OTHER
Dispute nr. 205
Opening date: Aug 22, 2020 2:23:40 PM
Dispute nr. 206
Opening date: Aug 23, 2020 12:31:04 PMCycle 16 report
Nothing interesting to report.
Summary
Total Cases in Cycle: 44 Closed: 39 Open: 5Cases
Dispute nr. 163 Opening date: Jul 24, 2020 1:31:05 PM Close date: Aug 1, 2020 10:24:59 PM Duration: 8 days, 8 hours, 53 minutes Summary notes: Parties completed trade normally Reason: OTHER Dispute nr. 164 Opening date: Jul 24, 2020 4:52:56 PM Close date: Aug 8, 2020 12:05:54 AM Duration: 14 days, 7 hours, 12 minutes Summary notes: Parties completed trade normally after USPS delay Reason: OTHER Dispute nr. 165 Opening date: Jul 25, 2020 4:48:16 PM Close date: Aug 2, 2020 11:10:23 PM Duration: 8 days, 6 hours, 22 minutes Summary notes: Parties agreed to cancel Reason: OTHER Dispute nr. 166 Opening date: Jul 25, 2020 7:14:24 PM Close date: Aug 2, 2020 11:10:59 PM Duration: 8 days, 3 hours, 56 minutes Summary notes: Parties completed trade normally Reason: OTHER Dispute nr. 167 Opening date: Jul 26, 2020 12:41:23 PM Close date: Aug 19, 2020 11:48:28 AM Duration: 23 days, 23 hours, 7 minutes Summary notes: Seller is unresponsive, buyer provided proof of payment Reason: NO_REPLY Dispute nr. 168 Opening date: Jul 27, 2020 7:56:21 PM Close date: Aug 23, 2020 9:39:53 AM Duration: 26 days, 13 hours, 43 minutes Summary notes: Seller confirms payment from Buyer, but unable to use in-app button to complete trade. Mediator to perform Manual Payout using private keys provided by both parties. Reason: BUG Dispute nr. 169 Opening date: Jul 27, 2020 8:24:41 PM Close date: Aug 2, 2020 11:17:31 PM Duration: 6 days, 2 hours, 52 minutes Summary notes: Buyer unresponsive, Seller can proceed to arbitration 20 days after trade began Reason: NO_REPLY Dispute nr. 170 Opening date: Jul 27, 2020 9:06:14 PM Close date: Jul 28, 2020 2:22:27 AM Duration: 5 hours, 16 minutes Summary notes: Parties agreed to cancel trade Reason: BANK_PROBLEMS Dispute nr. 171 Opening date: Jul 27, 2020 11:56:27 PM Close date: Aug 9, 2020 11:15:45 AM Duration: 12 days, 11 hours, 19 minutes Summary notes: Parties agreed to cancel Reason: OTHER Dispute nr. 172 Opening date: Jul 28, 2020 3:39:55 PM Close date: Aug 8, 2020 12:05:07 AM Duration: 10 days, 8 hours, 25 minutes Summary notes: Buyer did not send payment and did not respond to mediator Reason: NO_REPLY Dispute nr. 173 Opening date: Jul 28, 2020 9:22:04 PM Close date: Aug 2, 2020 11:19:05 PM Duration: 5 days, 1 hour, 57 minutes Summary notes: Parties completed trade normally Reason: OTHER Dispute nr. 174 Opening date: Jul 29, 2020 5:06:18 PM Close date: Jul 31, 2020 10:25:19 PM Duration: 2 days, 5 hours, 19 minutes Summary notes: Parties completed trade normally Reason: OTHER Dispute nr. 175 Opening date: Jul 29, 2020 10:12:07 PM Close date: Aug 4, 2020 11:08:51 PM Duration: 6 days, 0 hours, 56 minutes Summary notes: Parties agreed to cancel Reason: OTHER Dispute nr. 176 Opening date: Jul 30, 2020 3:48:15 AM Close date: Aug 2, 2020 11:36:08 PM Duration: 3 days, 19 hours, 47 minutes Summary notes: Parties completed trade normally Reason: OTHER Dispute nr. 177 Opening date: Jul 31, 2020 3:14:38 AM Close date: Aug 2, 2020 11:36:44 PM Duration: 2 days, 20 hours, 22 minutes Summary notes: Parties completed trade normally Reason: OTHER Dispute nr. 178 Opening date: Jul 31, 2020 5:33:19 AM Close date: Jul 31, 2020 10:26:08 PM Duration: 16 hours, 52 minutes Summary notes: Parties completed trade normally Reason: OTHER Dispute nr. 179 Opening date: Aug 2, 2020 4:54:01 AM Close date: Aug 7, 2020 11:59:30 PM Duration: 5 days, 19 hours, 5 minutes Summary notes: Parties completed trade normally Reason: OTHER Dispute nr. 180 Opening date: Aug 2, 2020 12:23:37 PM Close date: Aug 4, 2020 11:09:35 PM Duration: 2 days, 10 hours, 45 minutes Summary notes: Parties completed trade normally Reason: OTHER Dispute nr. 181 Opening date: Aug 2, 2020 4:20:27 PM Close date: Aug 7, 2020 11:56:25 PM Duration: 5 days, 7 hours, 35 minutes Summary notes: Parties completed trade normally after delay due to buyer forgot to press payment stared button Reason: OTHER Dispute nr. 182 Opening date: Aug 3, 2020 5:02:05 AM Close date: Aug 5, 2020 3:11:18 AM Duration: 1 day, 22 hours, 9 minutes Summary notes: Parties completed trade normally Reason: OTHER Dispute nr. 183 Opening date: Aug 3, 2020 10:21:37 PM Close date: Aug 5, 2020 9:40:52 PM Duration: 1 day, 23 hours, 19 minutes Summary notes: Parties completed trade normally, but payment method name did not match Reason: PROTOCOL_VIOLATION Dispute nr. 184 Opening date: Aug 4, 2020 5:58:01 AM Close date: Aug 5, 2020 3:13:06 AM Duration: 21 hours, 15 minutes Summary notes: Parties completed trade normally Reason: OTHER Dispute nr. 185 Opening date: Aug 5, 2020 5:49:34 PM Close date: Aug 7, 2020 11:55:46 PM Duration: 2 days, 6 hours, 6 minutes Summary notes: Parties completed trade normally after mempool delay Reason: USABILITY Dispute nr. 186 Opening date: Aug 6, 2020 12:57:53 AM Close date: Aug 7, 2020 11:53:22 PM Duration: 1 day, 22 hours, 55 minutes Summary notes: Failed trade Reason: USABILITY Dispute nr. 187 Opening date: Aug 6, 2020 10:44:44 AM Close date: Aug 7, 2020 11:51:54 PM Duration: 1 day, 13 hours, 7 minutes Summary notes: Parties completed trade normally after agreeing to waive bank name mismatch violation Reason: PROTOCOL_VIOLATION Dispute nr. 188 Opening date: Aug 7, 2020 7:51:04 AM Close date: Aug 7, 2020 11:58:49 PM Duration: 16 hours, 7 minutes Summary notes: Parties completed trade normally Reason: OTHER Dispute nr. 189 Opening date: Aug 7, 2020 6:56:20 PM Close date: Aug 12, 2020 1:55:52 AM Duration: 4 days, 6 hours, 59 minutes Summary notes: Parties completed trade normally Reason: OTHER Dispute nr. 190 Opening date: Aug 9, 2020 7:27:47 PM Close date: Aug 12, 2020 1:55:02 AM Duration: 2 days, 6 hours, 27 minutes Summary notes: Parties completed trade normally Reason: OTHER Dispute nr. 191 Opening date: Aug 10, 2020 6:38:04 AM Close date: Aug 11, 2020 1:00:05 AM Duration: 18 hours, 22 minutes Summary notes: Failed Trade Reason: OTHER Dispute nr. 192 Opening date: Aug 11, 2020 10:53:34 AM Close date: Aug 14, 2020 4:46:35 AM Duration: 2 days, 17 hours, 53 minutes Summary notes: Parties completed trade normally Reason: OTHER Dispute nr. 193 Opening date: Aug 11, 2020 10:11:53 PM Close date: Aug 14, 2020 3:53:54 AM Duration: 2 days, 5 hours, 42 minutes Summary notes: Parties completed trade normally Reason: OTHER Dispute nr. 194 Opening date: Aug 12, 2020 7:24:25 AM Close date: Aug 16, 2020 1:55:57 AM Duration: 3 days, 18 hours, 31 minutes Summary notes: Parties completed trade normally Reason: OTHER Dispute nr. 195 Opening date: Aug 12, 2020 11:22:50 AM Close date: Aug 14, 2020 3:52:33 AM Duration: 1 day, 16 hours, 29 minutes Summary notes: Mediator confirmed payment Reason: OTHER Dispute nr. 196 Opening date: Aug 15, 2020 5:04:54 AM Close date: Aug 17, 2020 8:46:04 AM Duration: 2 days, 3 hours, 41 minutes Summary notes: Parties comlpeted trade normally after mempool delay Reason: OTHER Dispute nr. 197 Opening date: Aug 16, 2020 4:49:50 AM Close date: Aug 19, 2020 10:51:58 PM Duration: 3 days, 18 hours, 2 minutes Summary notes: Parties agreed to cancel trade Reason: OTHER Dispute nr. 198 Opening date: Aug 16, 2020 11:22:14 AM Close date: Aug 17, 2020 8:44:39 AM Duration: 21 hours, 22 minutes Summary notes: Parties completed trade normally Reason: OTHER Dispute nr. 199 Opening date: Aug 16, 2020 3:09:40 PM Close date: Aug 19, 2020 10:51:36 PM Duration: 3 days, 7 hours, 41 minutes Summary notes: Parties completed trade normally Reason: OTHER Dispute nr. 200 Opening date: Aug 17, 2020 4:20:23 PM Dispute nr. 201 Opening date: Aug 17, 2020 4:20:59 PM Dispute nr. 202 Opening date: Aug 18, 2020 10:49:24 PM Close date: Aug 19, 2020 10:49:58 PM Duration: 1 day, 0 hours, 0 minutes Summary notes: Parties completed trade normally Reason: OTHER Dispute nr. 203 Opening date: Aug 20, 2020 2:43:40 AM Dispute nr. 204 Opening date: Aug 20, 2020 10:08:53 AM Close date: Aug 23, 2020 9:41:03 AM Duration: 2 days, 23 hours, 32 minutes Summary notes: Parties completed trade normally Reason: OTHER Dispute nr. 205 Opening date: Aug 22, 2020 2:23:40 PM Dispute nr. 206 Opening date: Aug 23, 2020 12:31:04 PM
@wiz For future cycle reports it is best to just keep it to an overall summary of how the cycle went so far. Otherwise it just becomes to long to analyze over time.
Bisq-knight
commented
4 years ago Nothing in particular to call out in this report. This cycle had slightly less trades in mediation (36, vs 52 last cycle) but the overall amount mediated was higher than last cycle (8.76 BTC vs 9.09 BTC).
Total Cases in Cycle: 36
Still open: 5
Closed: 31Total Cases in this Cycle: 40
Still open: 8
Closed: 32I will analyze the cycle up until today, will update it at the end of such cycle with the remaining information.
With the Revolut username there are now almost no cases regarding that payment method.
It is obvious that unanswered sellers are still our main cause of mediation disputes. We are currently assessing different options as to what seems to be the main driver for this. For now it looks as though some people don't mind losing their trade deposit, which seems weird considering some of these amounts are quite considerable.
*Another pending issue is the problem with users who never respond and trades that end up going to arbitration which makes no sense for the other party that often has done everything correctly. Similarly, a BTC seller may release the funds after 10 days with no penalty at all, there must be some way to control this.
wiz
commented
4 years ago Bisq-knight
commented
3 years ago I got an influx of cases in the past 2 days, which are still open. Nothing out of the ordinary, probably just spiked interest due to the price action of Bitcoin.
The cycle was pretty average. about 2 thirds of the value mediated was for altcoin trades (similar to previous cycles) and 1 for fiat trades (smaller trades in general).
The most common issue was simply traders going overtime but settling by themselves. Second
This cycle one of my past disputes ended in an unfuded arbitration/Reimbursement proposal (when there is no delayed payout tx, thus the trade amount does not get sent to the Bisq donation address).
Total Cases closed in Cycle: 21 (WIP)
Still open: 8
Total cases in cycle: 29Total Cases in this Cycle: 37
Still open: 7
Closed: 30I will analyze the cycle up until today, will update it at the end of such cycle with the remaining information.
This cycle there have been more cases than usual where seller's have not being able to confirm the payment due to the trade being stuck in stage two. (buyer's "payment made" button did not work on these cases) this is an issue that we've had in the past and was solved for the most part but for some reason there have been more cases lately.
Unresponsive sellers are still our main cause of mediation disputes.
*Another pending issue is the problem with users who never respond and trades that end up going to arbitration which makes no sense for the other party that often has done everything correctly. Similarly, a BTC seller may release the funds after 10 days with no penalty at all, there must be some way to control this.
huey735
commented
3 years ago Total Cases in this Cycle: 31
Still open: 6
Closed: 2573% User behaviour
15% Bank problems
12% Bug
This is my first cycle as a Mediator so I'm still getting my bearings. But traders not caring for the trade duration seems to be a trend. We probably should be more strict if we can to avoid this behaviour.
huey735
commented
3 years ago Total Cases in this Cycle: 36
Still open: 9
Closed: 2739% User behaviour
6% Bank problems - 2
55% Bug -
Bisq-knight
commented
3 years ago This cycle has been very problematic. Most cases I got are related to the issue of traders not being able to go through the workflow by themselves.
A couple of things that I am currently investigating that might be a problem in the coming cycle:
Total Cases closed in Cycle: 75 (WIP)
Still open: 20
Total cases in cycle: 95Total Cases in this Cycle: 73
Still open: 15
Closed: 58I will analyze the cycle up until today, will update it at the end of such cycle with the remaining information.
This cycle we've had more than double of our cycle average. It has been similar to the previous one in the sense that there have been more cases than usual where seller's have not being able to confirm the payment due to the trade being stuck in stage two. (buyer's "payment made" button did not work on these cases) this is an issue that we've had in the past and was solved for the most part but for some reason there have been more cases lately. the refresh button was taken away so that the real problem was solved.
I've been collecting bisq logs and sending them to developers to find out more about these bugs.
*Another pending issue is the problem with users who never respond and trades that end up going to arbitration which makes no sense for the other party that often has done everything correctly. Similarly, a BTC seller may release the funds after 10 days with no penalty at all, there must be some way to control this.
Bisq-knight
commented
3 years ago We're still dealing with multiple cases caused by the bug where traders could not press the button to move to the next stage.
This cycle was roughly the same in terms of distribution of reasons as last cycle, just slightly less (showing only closed cases based on the CSV report):
| Reason | Cycle 19 | Cycle 20 |
|---|---|---|
| BANK_PROBLEMS | 5 | 2 |
| BUG | 30 | 19 |
| OTHER | 16 | 13 |
| PEER_WAS_LATE | 10 | 10 |
| SELLER_NOT_RESPONDING | 4 | 2 |
| TRADE_ALREADY_SETTLED | 7 | 9 |
| USABILITY | 1 | |
| WRONG_SENDER_ACCOUNT | 2 | 1 |
| (empty) | 8 | |
| Total Result | 75 | 64 |
note: the CSV report has a few empty values, I'm talking to Chimp to figure if that's a definition issue or some problem generating the report or else, thus the discrepancy between 64 and 80 closed cases in the cycle.
Total Cases closed in Cycle: 80
Still open: 10
Total cases in cycle: 90I assume the empty ones are not closed cases... Otherwise which dispute nr. is it?
chimp1984
commented
3 years ago @leo816 @huey735 , @wiz Could you please all include the full report the way @Bisq-knight did it in cycle 20? Thanks. Can anyone also point out which bugs are the most frequent one (after 1.5.2.)? Maybe better to start with next cycle with that, as currenly most are from old/fixed bugs i assume.
leo816
commented
3 years ago In terms of volume of work this cycle has been similar to the last one. From what I've experienced, users have been a lot more engaging on keybase where I've been answering a lot of questions daily and users who have open mediations reach out to find out how they can avoid the problems they are having in the future.
Seller's having to open a mediation because they are unable to click on the "payment received" button has been the number one issue this cycle, it seems as though with the last update we are not seeing it as much, but it's too early to tell.
A big fix from the last update (v 1.5.2) has been the locked funds issue we had been seeing for a number of cases where the resync didn't work. after the new version all users with open cases updated and now it works perfectly.
| Reason | Cycle 20 |
|---|---|
| BANK_PROBLEMS | 3 |
| TX BUGGED | 7 |
| PAYMENT RECEIVED BUTTON | 33 |
| SELLER NOT RESPONDING | 14 |
| TRADE ALREADY SETTLED | 2 |
| WRONG SENDER ACCOUNT | 4 |
| Total Result | 63 |
Total Cases closed in Cycle: 63
Still open: 15
Total cases in cycle: 78Due to other stuff going on, I was unavailable to mediate Bisq trades for the past few months, and during this time my mediator key was not registered, so I only got a handful of cases re-opened. However, starting from cycle 21, I will re-register and resume duties as an active mediator.
huey735
commented
3 years ago | 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:
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.
Docs: https://bisq.wiki/Mediator Team: @bisq-network/mediators
Proposal for @leo816's bonded mediator role: GitHub Issue Approved DAO Proposal Transaction
Proposal for @Bisq-knight's bonded mediator role: GitHub Issue Approved DAO Proposal Transaction
Proposal for @pazza83's bonded mediator role: GitHub Issue Approved DAO Proposal Transaction