<p></p>
<blockquote>
<p><em>The XXXXX part in the issue title are the first characters of the Trade ID before the "-" (dash).</em></p>
</blockquote>
<p><a target="_blank" rel="noopener noreferrer" href="https://user-images.githubusercontent.com/82121390/113935800-3feac980-97f7-11eb-928c-4bfbf946044f.png"><img src="https://user-images.githubusercontent.com/82121390/113935800-3feac980-97f7-11eb-928c-4bfbf946044f.png" alt="image" style="max-width:100%;"></a></p>
<blockquote>
<p><em>The screenshot from the Bisq client must have the <strong>Trade ID</strong>, <strong>Deposit</strong>, <strong>Maker</strong> and <strong>Taker</strong> TXIDs visible. Of course some trades do not have all 3 types, that is ok. Make sure all private information is covered (like bank accounts, name, etc). <strong>Do not upload images where sensitive private data is visible!</strong></em></p>
</blockquote>
<p>Maker:  N/A<br>
Taker: N/A<br>
Deposit: N/A</p>
<blockquote>
<p><em>A reimbursement request has to contain textual representation of <strong>Maker</strong>, <strong>Taker</strong> and <strong>Deposit</strong> TXIDs (copy them from the client to the issue). <strong>All TXIDs that are visible in the screenshot must be copied to the issue in text form! Please use exact form for Maker/Taker/Deposit - no abbreviations like M:, T: or adding extra characters like "Maker TX:", etc. Leave those fields as they are and replace the "........" with the appropreate txid</strong></em></p>
</blockquote>
<p>Bisq version: 1.6.2<br>
BTC address for reimbursement: bc1qm3h5753k9s9kryhjglpgmvsk3tq2vpzu0lugex</p>
<blockquote>
<p><em>Provide the Bisq client version to help developers identify the causing issue.</em></p>
</blockquote>
<p>Other notes:</p>
<p>Trade ID: 3u21WSk-9db5870d-056d-4e66-bc63-5fbc179dcbac-159<br>
Trading peers onion address: bfsleo4jmle6noou7466d52tj2qea6cxgqa5t5zdekxceelgfvw2fmad.onion:9999<br>
Maker fee transaction ID: 6f1bfa1369356bf889f9e727fee7e7f2a8421533b141c123d7c265342e82265a</p>
<p>Further screenshots & error log file:</p>
<p><a href="https://github.com/bisq-network/support/files/6274607/bisq.20210704.2.txt">bisq 20210704 2.txt</a></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/support/issues/903">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNTNG5EOLLGHWXHZ3E3THTEA3ANCNFSM42RRZEWQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNSWRNSCYZGNI7I63ODTHTEA3A5CNFSM42RRZEW2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4MWVBXXQ.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/support/issues/903",
"url": "https://github.com/bisq-network/support/issues/903",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>