[bisq-network/bisq] Show warning if user has a pruned Bitcoin node locally running (#3273)

Christoph Atteneder notifications at github.com
Fri Feb 14 15:40:47 UTC 2020


@dmos62 @Kixunil Yes, I think if we detect a misconfiguration of the local bitcoin core node we should prompt the user if she wants to continue with the default configuration (using nodes provided by Bisq core contributors, public network is deactivated atm completely because of the potential v0.19+ problem) or if the user wants to quit Bisq. I wouldn't do any autoconfiguration as you probably need more write permissions (different per OS) and I personally wouldn't allow any app to just write anywhere on my system. Retry is a nice-to-have but not a must IMO. So in the simplest implementation it would be a warning with the options `Continue` and `Quit`.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/3273#issuecomment-586341602
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200214/384d23f0/attachment.html>


More information about the bisq-github mailing list