<p>Related to: <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="421868445" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/bisq/issues/2547" data-hovercard-type="issue" data-hovercard-url="/bisq-network/bisq/issues/2547/hovercard" href="https://github.com/bisq-network/bisq/issues/2547">#2547</a>, possibly <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="414939024" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/bisq/issues/2474" data-hovercard-type="issue" data-hovercard-url="/bisq-network/bisq/issues/2474/hovercard" href="https://github.com/bisq-network/bisq/issues/2474">#2474</a>, <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="403767347" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/bisq/issues/2327" data-hovercard-type="issue" data-hovercard-url="/bisq-network/bisq/issues/2327/hovercard" href="https://github.com/bisq-network/bisq/issues/2327">#2327</a></p>
<p>This is a slightly edited re-post of the issue reported at:<br>
<a href="https://bisq.community/t/issue-bisq-startup-problem-on-slow-networks-3-4-problem/7233/3" rel="nofollow">https://bisq.community/t/issue-bisq-startup-problem-on-slow-networks-3-4-problem/7233/3</a></p>
<p><strong>Details:</strong><br>
After a network congestion/degradation during startup (issue <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="421868445" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/bisq/issues/2547" data-hovercard-type="issue" data-hovercard-url="/bisq-network/bisq/issues/2547/hovercard" href="https://github.com/bisq-network/bisq/issues/2547">#2547</a>), Bisq remains in a dead-end state that doesn't recover even after the network performance is restored. The only way to recover is restarting the program.<br>
This condition is not properly handled nor reported in the UI, causing confusion to unaware users.</p>
<p><strong>Steps to reproduce</strong></p>
<ul>
<li>same as issue <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="421868445" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/bisq/issues/2547" data-hovercard-type="issue" data-hovercard-url="/bisq-network/bisq/issues/2547/hovercard" href="https://github.com/bisq-network/bisq/issues/2547">#2547</a>, start with a working installation</li>
<li>close application</li>
<li>degrade network: <code>sudo tc qdisc add dev eth0 root tbf rate 100kbit burst 1540 latency 50ms</code></li>
<li>start application</li>
<li>wait 3 hours, per issue <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="421868445" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/bisq/issues/2547" data-hovercard-type="issue" data-hovercard-url="/bisq-network/bisq/issues/2547/hovercard" href="https://github.com/bisq-network/bisq/issues/2547">#2547</a> there should be no progress past step 3/4</li>
<li>remove network degradation: <code>sudo tc qdisc del ...</code></li>
<li>wait indefinitely, there will still be no progress past step 3/4, even 12 hours later</li>
</ul>
<p><strong>Expected result</strong><br>
The program should attempt to recover seamlessly from the degraded state when the network conditions allow it.</p>
<p><strong>Alternative expected result</strong><br>
The program should detect the dead-end state and report it in the UI along with some information about its probable cause, then exit or restart in order to attempt to recover from this state.</p>
<p><strong>Actual result</strong><br>
The program keeps running and displays a progress indicator and shows the offers, trades, wallet contents, exchange rates etc, creating a false appearance of almost-operational and a false expectation of further progress, when in reality it is in an unrecoverable no-op state.</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/2549">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AkpZtlbr_UrFyx0Wy-eApAtxllDZyroXks5vXb8XgaJpZM4b4Kt8">mute the thread</a>.<img src="https://github.com/notifications/beacon/AkpZttkAskXwVGX4SQqIyBuU26X0cJdIks5vXb8XgaJpZM4b4Kt8.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/bisq-network/bisq","title":"bisq-network/bisq","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/bisq-network/bisq"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"Unhandled unrecoverable program state following failed seed handshake (#2549)"}],"action":{"name":"View Issue","url":"https://github.com/bisq-network/bisq/issues/2549"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/bisq/issues/2549",
"url": "https://github.com/bisq-network/bisq/issues/2549",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>