<p></p>
<h1>Cycle 26 Report</h1>
<p>l'll break down the distribution of the  mediation cases I've handled in Cycle 26, the main <em>BUGS</em> are:</p>
<ul>
<li>
<p><strong>Java Heap Error</strong><br>
It prevented me from accessing my tickets or responding for a short period of time.</p>
</li>
<li>
<p><strong>Messages not arriving to peer</strong><br>
Still not completely solved and we will continue to work and solve this</p>
</li>
<li>
<p><strong>Funds showing as locked when the trade fails</strong>: SPV resync doesn't always fix this, when this happens the easiest is to delete the ClosedTrades and FailedTrades files in the db folder.**:</p>
</li>
<li>
<p><strong>BTC seller being unable to confirm that they received the payment or stuck in stage 2.</strong>:</p>
</li>
</ul>
<p>This is the most common issue, it happens because either the seller can't confirm as the button is greyed out withing the payment period or because the trade appears to be stuck in stage 2, even though the buyer clicked on "payment started".   We will keep providing logs to try and get this solved.</p>
<p>The following issues sometimes happen but every cycle the occur less:</p>
<ul>
<li>
<p><strong>The Taker fee and Deposit transactions weren't properly broadcast.</strong></p>
</li>
<li>
<p><strong>The Deposit and Payout transactions weren't properly constructed.</strong></p>
</li>
<li>
<p><strong>Trader's Bisq client showed the trade as failed despite the opposite being true.</strong></p>
</li>
</ul>
<p>the "seller not responding" Category also includes trades that are settled past the payment period and where the seller can't confirm because the button is greyed out as it should be.</p>
<p>The following table is not updated because the report button isn't working on my mediation side.</p>
<p>I had a total of 42 mediation cases. The number is considerably less because of the incorporation of Pazza as mediator this cycle.</p>
<table role="table">
<thead>
<tr>
<th>Reason</th>
<th>Cycle 26</th>
</tr>
</thead>
<tbody>
<tr>
<td>LATE_PAYMENTS</td>
<td>13</td>
</tr>
<tr>
<td>BANK_PROBLEMS</td>
<td>4</td>
</tr>
<tr>
<td>TX BUGGED</td>
<td>8</td>
</tr>
<tr>
<td>PAYMENT RECEIVED BUTTON</td>
<td>17</td>
</tr>
<tr>
<td>SELLER NOT RESPONDING</td>
<td>9</td>
</tr>
<tr>
<td>BUYER NOT RESPONDING</td>
<td>4</td>
</tr>
<tr>
<td>TRADE ALREADY SETTLED</td>
<td>19</td>
</tr>
<tr>
<td>WRONG SENDER ACCOUNT</td>
<td>2</td>
</tr>
<tr>
<td>FUNDS STUCK IN THE MULTISIG</td>
<td>5</td>
</tr>
<tr>
<td>Total Result</td>
<td>81</td>
</tr>
</tbody>
</table>
<p>(the table above is not updated)</p>
<pre><code>Total Cases closed in Cycle 26: 38
Still open: 4
Total cases in cycle 26: 42
</code></pre>
<p>.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/roles/issues/83#issuecomment-885486371">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNTLREHNY6QY6USCOR3TZESKFANCNFSM4HAKQX4Q">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNVQXKPLPFIECHXP3ADTZESKFA5CNFSM4HAKQX42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGTDXGIY.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/roles/issues/83#issuecomment-885486371",
"url": "https://github.com/bisq-network/roles/issues/83#issuecomment-885486371",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>