<p></p>
<h3><strong>Cycle 14 Report</strong></h3>
<pre><code>Total Cases in this Cycle: 38
Still open: 10
Closed: 28
</code></pre>
<blockquote>
<p>Because 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.</p>
</blockquote>
<p>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.</p>
<ul>
<li>
<p>35% Banking issues (Revolut, Zelle, SEPA)</p>
</li>
<li>
<p>15% both parties agreed to cancel</p>
</li>
<li>
<p>35% BTC seller took longer to answer/make the payment</p>
</li>
<li>
<p>15% Unexperience, parties unsure of how the process works</p>
</li>
</ul>
<p>This cycle we've had a considerable amount of issues with Revolut between <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/Bisq-knight/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/Bisq-knight">@Bisq-knight</a> 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 (<a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/example/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/example">@example</a>) or if none of these work just making a normal transfer using the IBAN revolution provides.</p>
<p>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.</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-645711365">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNRDPHHBOSBQ777LGCDRXFTSLANCNFSM4HAKQX4Q">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNQSFZKDH4FV3VY7WMLRXFTSLA5CNFSM4HAKQX42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEZ6MMBI.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-645711365",
"url": "https://github.com/bisq-network/roles/issues/83#issuecomment-645711365",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>