<p></p>
<p>Step 3 in this scheme isn't safe. A buyer could just be unresponsive for 25 days and then send the funds to themselves. The seller have no way of telling if the buyer's silence is malicious or not so the seller has to take the case to arbitration.</p>
<p>This problem was touched on in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="738275611" data-permission-text="Title is private" data-url="https://github.com/bisq-network/proposals/issues/279" data-hovercard-type="issue" data-hovercard-url="/bisq-network/proposals/issues/279/hovercard" href="https://github.com/bisq-network/proposals/issues/279">#279</a> (single tx trade protocol). It would be possible to add an intermediate step to handle this:</p>
<ol>
<li>Day 0: trade initiated. Two symmetric payout transaction paths are presigned, first step can be published after 20 days</li>
<li>Day 20: either peer can publish their payout path<br>
i. Buyer publishes their payout of the deposit tx<br>
ii. Seller publishes their payout of the deposit tx</li>
<li>Day 20-25:<br>
i. Seller can spend the tx from 2.i to initiate arbitration.<br>
ii. Buyer can spend the tx from 2.ii to initiate arbitration.</li>
<li>Day 25+:<br>
i. Buyer can spend the tx from 2.i to themselves, if arbitration wasn't initiated by seller.<br>
ii. Seller can spend the tx from 2.ii to themselves, if arbitration wasn't initiated by buyer.</li>
</ol>
<p>With this kind of protocol there is no risk of either party staying silent to trick the other to wait and avoid arbitration. Once the intermediate step is published after day 20 it's up to the other peer to take it to arbitration or lose the funds.</p>
<p>This protocol adds another 1.5 rounds to the trade protocol if I remember correctly. That's an added risk of trades failing during the take offer process.</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/proposals/issues/303#issuecomment-772443868">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNU5WACCNE5D2ECQRFTS5EYNHANCNFSM4W6V4MCA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNWBLKI4KUO244FDLMLS5EYNHA5CNFSM4W6V4MCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFYFI5XA.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/proposals/issues/303#issuecomment-772443868",
"url": "https://github.com/bisq-network/proposals/issues/303#issuecomment-772443868",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>