<p></p>
<h1>Cycle 28 Report</h1>
<p>l'll break down the distribution of the  mediation cases I've handled in Cycle 28, the main <em>BUGS</em> are:</p>
<ul>
<li>
<p><strong>Banking Issues</strong><br>
Banks not accepting payments, Monthly payment limit allowed, Making a payment from the wrong account.</p>
</li>
<li>
<p><strong>Messages not arriving to peer</strong><br>
It seems it has to do with the Hibernating mode, currently preparing a fix to 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 issue has been fixed for the most part, all problems with users not being able to move from stage 2 to 3 have to do with the payment period having expired</p>
<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>
<table role="table">
<thead>
<tr>
<th>Reason</th>
<th>Cycle 28</th>
</tr>
</thead>
<tbody>
<tr>
<td>PEER_WAS_LATE</td>
<td>19</td>
</tr>
<tr>
<td>BANK_PROBLEMS</td>
<td>14</td>
</tr>
<tr>
<td>TX BUGGED</td>
<td>3</td>
</tr>
<tr>
<td>PAYMENT RECEIVED BUTTON</td>
<td></td>
</tr>
<tr>
<td>SELLER NOT RESPONDING</td>
<td>2</td>
</tr>
<tr>
<td>BUYER NOT RESPONDING</td>
<td>1</td>
</tr>
<tr>
<td>TRADE_ALREADY_SETTLED</td>
<td>4</td>
</tr>
<tr>
<td>WRONG SENDER ACCOUNT</td>
<td>4</td>
</tr>
<tr>
<td>OTHER</td>
<td>6</td>
</tr>
<tr>
<td>Total Result</td>
<td>53</td>
</tr>
</tbody>
</table>
<p>(the table above is not updated)</p>
<pre><code>Total Cases closed in Cycle 28: 47
Still open: 6
Total cases in cycle 28: 53
</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-923895771">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNQ2KM4B6KEC2GLGKF3UDBUY5ANCNFSM4HAKQX4Q">unsubscribe</a>.<br />Triage notifications on the go with GitHub Mobile for <a href="https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675">iOS</a> or <a href="https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub">Android</a>.
<img src="https://github.com/notifications/beacon/AJFFTNRXLXN2TGHXDFH7BUDUDBUY5A5CNFSM4HAKQX42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOG4IYPWY.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-923895771",
"url": "https://github.com/bisq-network/roles/issues/83#issuecomment-923895771",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>