<p>Well to be brutally honest, the approach of trusting 0-conf TXs to accept Bisq trade offers isn't feasible either. How else can we solve this fundamental design flaw in the Bisq trade protocol, if not to delay accepting the offer by a few seconds until Bisq can verify the 0-conf TX is actually in the Bitcoin mempool? It seems to fix this properly would require re-architecting the trade protocol quite a bit.</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/3489?email_source=notifications&email_token=AJFFTNTCOJMJ7TRMOZ26FVTQRL3ORA5CNFSM4JFREWE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECYHCYQ#issuecomment-548434274">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNRRUOYPEQBBRODTPTTQRL3ORANCNFSM4JFREWEQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNXY5ZJPIBXYMHQ7GNTQRL3ORA5CNFSM4JFREWE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECYHCYQ.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/3489?email_source=notifications\u0026email_token=AJFFTNTCOJMJ7TRMOZ26FVTQRL3ORA5CNFSM4JFREWE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECYHCYQ#issuecomment-548434274",
"url": "https://github.com/bisq-network/bisq/issues/3489?email_source=notifications\u0026email_token=AJFFTNTCOJMJ7TRMOZ26FVTQRL3ORA5CNFSM4JFREWE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECYHCYQ#issuecomment-548434274",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>