[bisq-network/bisq] Not allow bitcoinj to auto connect to localhost when localhost was not detected by client (#3783)

Christoph Atteneder notifications at github.com
Thu Dec 12 19:00:49 UTC 2019


> This would only fail for users that run full bitcoind nodes locally, right?

Yes

> What is the workaround if a user encounters this? restart?

Should solve the problem also if you have a transaction already in limbo. Unfortunately for me it wasn't solved with a restart and after a SPV resync the transaction was removed by bitcoinj.

> Is waiting for the Jan release sufficient or is this a hotfix candidate?

I don't think this is something new, so I think it should be fine to ship it in the next release.

-- 
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/pull/3783#issuecomment-565138923
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191212/bca5b4a7/attachment.html>


More information about the bisq-github mailing list