<p></p>
<p>In terms of the trading protocol, it appears to be operating properly, i.e. attempting to deliver <code>CCTSM</code>* to your trading peer.  In terms of the UI it does look a bit glitchy if you close/restart the Bisq app, it resends <code>CCTSM</code> and the trade state jumps back to 2 and then moves again to 3 as you mentioned.  The button for stage 2 is shown and can even be pressed which all adds to the confusion.  So yes, that could be improved upon, but I'll re-iterate that the protocol seems to be functioning fine.  In my testing this scenario only happens if the peer is offline and has yet to receive that <code>CCTSM</code> message and the Bisq app is restarting.<br>
_{* CCTSM = CounterCurrencyTransferStartedMessage}</p>
<p>We can leave this issue open so that it can be addressed when resources become available.</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/4864#issuecomment-735564679">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNQLASWXNCSJXAFN7DTSSMXQ5ANCNFSM4UFZYBIA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNUAFWLZ47XCBDGEHPLSSMXQ5A5CNFSM4UFZYBIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFPL5HBY.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/4864#issuecomment-735564679",
"url": "https://github.com/bisq-network/bisq/issues/4864#issuecomment-735564679",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>