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

<!-- This issue tracker is only for technical issues related to Bitcoin Core. General bitcoin questions and/or support requests are best directed to the Bitcoin StackExchange at https://bitcoin.stackexchange.com. For reporting security issues, please read instructions at https://bitcoincore.org/en/contact/. If the node is "stuck" during sync or giving "block checksum mismatch" errors, please ensure your hardware is stable by running memtest and observe CPU temperature with a load-test tool such as linpack before creating an issue! -->

<!-- Describe the issue -->

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.

<!--- What behavior did you expect? -->

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

<!--- What was the actual behavior (provide screenshots if the issue is GUI-related)? -->

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.

<!--- How reliably can you reproduce the issue, what are the steps to do so? -->

Versions used: Bisq 1.2.3

<!-- What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)? -->

Bitcoin Core 0.19.0.1 from bitcoin core website

<!-- Any extra information that might be useful in the debugging process. -->

<!--- This is normally the contents of a `debug.log` or `config.log` file. Raw text or a link to a pastebin type site are preferred. -->

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.

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

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

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

Should this not be an issue in the Bisq repository rather than Bitcoin Core? It was known ahead of time that the v0.19 release would disable BIP37 & BIP111 by default, and this is an issue with Bisq not Bitcoin Core.

Yes, it's a documentation issue at most, and I think that documentation belongs in BISQ's setup documentation. This repository is not a place it will be seen.

If this would have been reported to us (say, in the rc phase), that this would require a change of settings for BISQ, it could have been mentioned specifically in the release notes. It was of course mentioned that -peerbloomfilters is now disabled by default.