# Bisq cannot connect to Bitcoin Node on Version 0.19

**URL:** <https://bisq.community/t/bisq-cannot-connect-to-bitcoin-node-on-version-0-19/8763>\
**Category:** Support\
**Created:** [November 25, 2019, 10:09am UTC](https://bisq.community/t/bisq-cannot-connect-to-bitcoin-node-on-version-0-19/8763 "2019-11-25T10:09:43Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![esackbauer](https://bisq.community/letter_avatar/esackbauer/32/5_5575768a8748004e209b776fc1b2916d.png) [@esackbauer](https://bisq.community/u/esackbauer)\
**Post date:** [November 25, 2019, 10:09am UTC](https://bisq.community/t/bisq-cannot-connect-to-bitcoin-node-on-version-0-19/8763/1 "2019-11-25T10:09:43Z")

</div>

Since I upgraded my bitcoin node to version 0.19.0.1, Bisq does not connect to the node anymore:

Nov.-25 11:04:17.813 [PeerGroup Thread] INFO o.b.c.PeerGroup: Attempting connection to [10.x.y.z]:8333 (0 connected, 1 pending, 1 max)  
Nov.-25 11:04:17.817 [NioClientManager] INFO o.b.n.NioClientManager: Connected to /10.x.y.z:8333  
Nov.-25 11:04:17.818 [NioClientManager] INFO o.b.core.Peer: Announcing to /10.x.y.z:8333 as: /bitcoinj:0.14.7.bisq.1-SNAPSHOT/Bisq:1.2.3/  
Nov.-25 11:04:17.818 [NioClientManager] INFO o.b.c.PeerGroup: [10.x.y.z]:8333: Peer died (0 connected, 0 pending, 1 max)  
Nov.-25 11:04:17.824 [PeerGroup Thread] INFO o.b.c.PeerGroup: Peer discovery took 5.099 μs and returned 0 items

the bitcoin node is running and accepting connections from other clients/nodes

Edit: There seems to be a breaking change in v 0.19:

> To eliminate well-known denial-of-service vectors in Bitcoin Core, especially for nodes with spinning disks, the default value for the `-peerbloomfilters` configuration option has been changed to false. This prevents Bitcoin Core from sending the BIP111 NODE\_BLOOM service flag, accepting BIP37 bloom filters, or serving merkle blocks or transactions matching a bloom filter. Users who still want to provide bloom filter support may either set the configuration option to true to re-enable both BIP111 and BIP37 support or enable just BIP37 support for specific peers using the updated `-whitelist` and `-whitebind` configuration options described elsewhere in these release notes. For the near future, lightweight clients using public BIP111/BIP37 nodes should still be able to connect to older versions of Bitcoin Core and nodes that have manually enabled BIP37 support, but developers of such software should consider migrating to either using specific BIP37 nodes or an alternative transaction filtering system. (#16152)

Workaround:  
Connect to an older bitcoin core node, or to one which has either peerbloomfilter=1 set or whitebind/whitelist with permission “bloomfilter” for your network.

---

<div class="post-metadata">

**Author:** ![esackbauer](https://bisq.community/letter_avatar/esackbauer/32/5_5575768a8748004e209b776fc1b2916d.png) [@esackbauer](https://bisq.community/u/esackbauer)\
**Post date:** [November 25, 2019, 12:36pm UTC](https://bisq.community/t/bisq-cannot-connect-to-bitcoin-node-on-version-0-19/8763/2 "2019-11-25T12:36:16Z")

</div>

is now tracked here:

> <https://github.com/bitcoin/bitcoin/issues/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! --\>
> 
> 
> 
> 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.

---

<div class="post-metadata">

**Author:** ![devin](https://bisq.community/letter_avatar/devin/32/5_5575768a8748004e209b776fc1b2916d.png) [@devin](https://bisq.community/u/devin)\
**Post date:** [November 26, 2019, 9:00am UTC](https://bisq.community/t/bisq-cannot-connect-to-bitcoin-node-on-version-0-19/8763/3 "2019-11-26T09:00:09Z")

</div>

As you found, a change in configuration is necessary to the node for SPV wallets to function. So you might want to close the issue in the bitcoin repo since it isn’t really an issue.

---

<div class="post-metadata">

**Author:** ![esackbauer](https://bisq.community/letter_avatar/esackbauer/32/5_5575768a8748004e209b776fc1b2916d.png) [@esackbauer](https://bisq.community/u/esackbauer)\
**Post date:** [November 26, 2019, 3:48pm UTC](https://bisq.community/t/bisq-cannot-connect-to-bitcoin-node-on-version-0-19/8763/4 "2019-11-26T15:48:09Z")

</div>

> [@devin](#):
>
> SPV

I don’t know if thats the right approach, as the majority of nodes will sooner or later have no peerbloomfilters active. At least this needs to be officially documented, especially for people like me, running their own nodes.

And Bitcoincore explicitly wrote “developers of such software [like Bisq] should consider migrating to either using specific BIP37 nodes or an alternative transaction filtering system.”

This issue is already confirmed for 2.x release of Bisq.

---

<div class="post-metadata">

**Author:** ![devin](https://bisq.community/letter_avatar/devin/32/5_5575768a8748004e209b776fc1b2916d.png) [@devin](https://bisq.community/u/devin)\
**Post date:** [November 27, 2019, 12:32am UTC](https://bisq.community/t/bisq-cannot-connect-to-bitcoin-node-on-version-0-19/8763/5 "2019-11-27T00:32:32Z")

</div>

I agree we need to document the necessary configuration for users that want to run their own full node. I have created a task: [https://github.com/bisq-network/bisq-docs/issues/181](https://github.com/bisq-network/bisq-docs/issues/181)

Yes, Bisq may need to find an alternative solution potentially before V2. But my point is there is nothing for bitcoin core to do, so no need to open an issue there.