<h3>Description</h3>
<p>Bisq V 1.2.3<br>
Trade had become stuck waiting for blockchain confirmation. A support ticket was created using ctrl+O. The mediator suspected the problem was due to the fee being too low. The support ticket was eventually closed and a payout issued. User accepted the payout from the mediator from Open Trades. The BTC appears in users wallet but the trade remained listed in Open Trades and the BTC was locked in a trade.</p>
<p>Bisq V1.2.4<br>
After upgrade upon first start of Bisq App user is prompted about an open trade (0BHgBN) being in a problem state and was prompted to move the trade to Failed Trades. User accepted the request and the trade was now moved from Open Trades to Failed Trades. The BTC that was previously locked in trade now disappeared from users wallet.</p>
<h4>Version</h4>
<p>1.2.4</p>
<h3>Steps to reproduce</h3>
<p>Look at trade 0BHgBN for an example of this problem. User lost 0.157605 bitcoin from wallet.</p>
<p>Arbitrators payout was issued as follows:<br>
Ticket closed on 22 Nov 2019 10:50:29<br>
Summary:<br>
Payout amount for BTC buyer: 0.015010 BTC<br>
Payout amount for BTC seller: 0.157605 BTC<br>
Summary notes:<br>
Not published tx.<br>
Next steps:<br>
Open trade and accept or reject suggestion from mediator</p>
<h3>Expected behaviour</h3>
<p>The Payout amount for BTC seller: 0.157605 BTC should have gone back to users wallet after the trade was moved from Open Trades to Failed trades.</p>
<h3>Actual behaviour</h3>
<p>The Payout amount for BTC seller: 0.157605 BTC was lost from the users wallet. It was previously showing as Locked in Trade and vanished completely after the trade was moved to Failed trades.</p>
<h3>Screenshots</h3>
<p><a target="_blank" rel="noopener noreferrer" href="https://user-images.githubusercontent.com/2623245/70886738-21ded180-1fd4-11ea-803b-3dbb55e086c5.png"><img src="https://user-images.githubusercontent.com/2623245/70886738-21ded180-1fd4-11ea-803b-3dbb55e086c5.png" alt="0BHgBN-Failed-Trade-Screenshot_2019-12-11_14-31-36" style="max-width:100%;"></a><br>
<a target="_blank" rel="noopener noreferrer" href="https://user-images.githubusercontent.com/2623245/70886759-2c996680-1fd4-11ea-8744-134e743ccd63.png"><img src="https://user-images.githubusercontent.com/2623245/70886759-2c996680-1fd4-11ea-8744-134e743ccd63.png" alt="0BHgBN-Fees-Screenshot_2019-12-13_06-44-35" style="max-width:100%;"></a></p>
<h4>Device or machine</h4>
<p>Qubes OS V 3.2.1<br>
Dell Inspiron Laptop</p>
<h4>Additional info</h4>
<p>Bisq Logs are attached here:</p>
<p><a href="https://github.com/bisq-network/bisq/files/3966553/bisqLogs.zip">bisqLogs.zip</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/bisq/issues/3794?email_source=notifications&email_token=AJFFTNQ3DLBB3OBACATUV5TQY4V3BA5CNFSM4J3FUMI2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IAU3NHA">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNSCLTMZHYEGTSKT2KDQY4V3BANCNFSM4J3FUMIQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNRVTPQTUVR6Q3KS6R3QY4V3BA5CNFSM4J3FUMI2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IAU3NHA.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/bisq/issues/3794?email_source=notifications\u0026email_token=AJFFTNQ3DLBB3OBACATUV5TQY4V3BA5CNFSM4J3FUMI2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IAU3NHA",
"url": "https://github.com/bisq-network/bisq/issues/3794?email_source=notifications\u0026email_token=AJFFTNQ3DLBB3OBACATUV5TQY4V3BA5CNFSM4J3FUMI2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IAU3NHA",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>