Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bisq cannot connect to Bitcoin Core v0.19 in default settings #17589

Open
esackbauer opened this issue Nov 25, 2019 · 3 comments
Labels

Comments

@esackbauer
Copy link

@esackbauer esackbauer commented Nov 25, 2019

Description of issue:
Since Bitcoin Core release 0.19, BIP111 and BIP37 (peerbloomfilters) are deactivated by default.
Because of this, Bisq cannot connect to any node running on 0.19 in default config.

Expected outcome:
Bisq should connect to any Bitcoin core node with recent release.

Steps to reproduce:

  1. Configure Bisq to use a certain node running v 0.19 (I used my own node)
  2. Starting Bisq results in not getting connected.

Versions used:
Bisq 1.2.3

Bitcoin Core 0.19.0.1
from bitcoin core website

Link to change log describing new default settings for BIP111 and BIP37 (see "P2P changes"):
https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-0.19.0.1.md

Workaround: Use a node which has "peerbloomfilters=1" set. Whitelisting did not work for me.

@esackbauer esackbauer added the Bug label Nov 25, 2019
@laanwj laanwj added P2P Upstream and removed Bug labels Nov 25, 2019
@TheBlueMatt

This comment has been minimized.

Copy link
Contributor

@TheBlueMatt TheBlueMatt commented Nov 27, 2019

This seems like an issue with release notes or whitelisting? How did you try to whitelist (whitebind? whitelist? etc).

@esackbauer

This comment has been minimized.

Copy link
Author

@esackbauer esackbauer commented Nov 27, 2019

This seems like an issue with release notes or whitelisting? How did you try to whitelist (whitebind? whitelist? etc).

I couldn't find a hint in the Bisq documentation that BIP37 is mandatory.
I tried now whitelisting my client network 192.168.1.0/24 (where also my bitcoin node is running), it works with:
whitelist=bloomfilter@192.168.1.0/24

@esackbauer esackbauer closed this Nov 27, 2019
@esackbauer esackbauer reopened this Nov 27, 2019
@lockhartheavyindustries

This comment has been minimized.

Copy link

@lockhartheavyindustries lockhartheavyindustries commented Dec 6, 2019

FWIW, if you're running Bisq and bitcoind on the same box, I found that this worked fine also:

whitelist = bloomfilter@127.0.0.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.