[bisq-network/bisq] Bisq stalls for 10 seconds while starting during Bitcoin node detection if firewall enabled (#4073)

Christoph Atteneder notifications at github.com
Wed Mar 18 10:40:41 UTC 2020

@dmos62 I have the feeling the fixing of the wrong used `detected` value before that is now solved  automatically by the `null` check might cause this issue. 
We have fixed the issue that it defaulted back then to `true` without having the detection set, but this change might cause other issues. I think that is also the reason why at following code part the local bitcoin flag is checked again.

Maybe the safer solution would be to update the `useTorForBTC` in the WalletSetup after doing the first detection during the Bisq startup sequence introducing again at step2 the local bitcoin node check. What do you think?

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200318/fecceaf2/attachment.html>

More information about the bisq-github mailing list