[bisq-network/bisq-core] Fixes issue 1566 (#119)

[Manfred Karrer]

I have not investigated it more closely but from my experience it connects to Bitcoin core while syncing. Maybe it depends on the current sync state of Bitcoin core? Bisq basically just try to connect to localhost on the default port and if it can connect it assumes Bitcoin Core is running.
In one of the next versions the UI will have the option to set pruned mode in Bitcoin Core and then more people might get that problem (as reported from a user who could not get Bisq synced as he had a pruned node running).
Its a more complex topic in all as pruned nodes could still provide data depending on the depth of the pruning and the age of the Bisq wallet... No clear idea how to deal with that and I doubt we can detect that...

-- 
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-core/pull/119#issuecomment-395010649
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180606/faffa03b/attachment.html>