<p>As Bisq is not a full node wallet, it must connect to a full node in order to be able to receive transactions and learn when a transaction confirms. Without a local instance of Bitcoin Core, it will simply connect to a random node on the internet (there are some built in discovery methods for how it can find a node to connect to). If Bisq detects that you are running a node locally (i.e. you are running Bitcoin Core as well), it will instead connect to your local node and get its information from there.</p>
<p>Since Bisq relies on BIP 37 which Bitcoin Core has turned off by default since 0.19.0, you will need to enable this feature by adding <code>peerbloomfilters=1</code> to your <code>bitcoin.conf</code> file. Otherwise Bisq will be unable to receive Bitcoin transactions. This is likely the syncing issues you are running into.</p>
<p>For some more information about local node settings in Bisq, you can read <a href="https://bisq.wiki/Connecting_to_your_own_Bitcoin_node" rel="nofollow noreferrer">https://bisq.wiki/Connecting_to_your_own_Bitcoin_node</a>.</p>

CC BY-SA 4.0
2020-11-26T13:44:10.120Z
Can I ask why exactly Bisq would be relying on some weird Google-made BIP from 2012 when even Bitcoin Core has (apparently) rejected it?
J. Lotz
CC BY-SA 4.0
2020-11-26T17:24:43.590Z
The BIP was made by a person who was working at Google at that time, but it is not a Google made BIP. BIP 37 was the primary way to implement SPV and Bitcoin Core implemented it for a long time. However there are alternative SPV methods now such as BIP 157/158, but many older software still rely on BIP 37.
Ava Chow
CC BY-SA 4.0
2023-01-18T07:32:41.313Z
Is there some security risk on enabling this flag in bitcoin node? (https://github.com/bitcoin/bitcoin/issues/9540)
thevikas
CC BY-SA 4.0
2020-11-26T05:49:57.410Z
2020-11-26T05:49:57.410Z
Ava Chow
<p>What exactly is the relation between between Bisq and Bitcoin Core? It seems like Bisq can function perfectly well without Bitcoin Core, but if you do run Bitcoin Core at the same time, it appears to have issues (sometimes) with syncing the Bitcoin network. (Whatever that means in terms of Bisq, since it's clearly not a fullnode Bitcoin wallet.)</p>
<p>I've tried to figure, read and ask my away to the answer to this question for a long time now, but I've just been ignored.</p>
<p>In what technical/concrete ways does Bisq use/depend on Bitcoin Core, other than allowing you to easily click a button inside of Bisq to open up Bitcoin Core with the fields pre-filled in?</p>
<p>If it works without Bitcoin Core installed, is there some benefit in allowing Bisq to &quot;utilize&quot; Bitcoin Core?</p>

<bitcoin-core><decentralized-exchanges><bisq>
What exactly is the relation between Bisq and Bitcoin Core?
J. Lotz
# What exactly is the relation between Bisq and Bitcoin Core?

(Asked by: username_0 on 2020-11-26)

What exactly is the relation between between Bisq and Bitcoin Core? It seems like Bisq can function perfectly well without Bitcoin Core, but if you do run Bitcoin Core at the same time, it appears to have issues (sometimes) with syncing the Bitcoin network. (Whatever that means in terms of Bisq, since it's clearly not a fullnode Bitcoin wallet.)

I've tried to figure, read and ask my away to the answer to this question for a long time now, but I've just been ignored.

In what technical/concrete ways does Bisq use/depend on Bitcoin Core, other than allowing you to easily click a button inside of Bisq to open up Bitcoin Core with the fields pre-filled in?

If it works without Bitcoin Core installed, is there some benefit in allowing Bisq to "utilize" Bitcoin Core?

**Tags:** bitcoin-core, decentralized-exchanges, bisq


---

## 1 answers

### Answer by username_1 on 2020-11-26. Score: 1

As Bisq is not a full node wallet, it must connect to a full node in order to be able to receive transactions and learn when a transaction confirms. Without a local instance of Bitcoin Core, it will simply connect to a random node on the internet (there are some built in discovery methods for how it can find a node to connect to). If Bisq detects that you are running a node locally (i.e. you are running Bitcoin Core as well), it will instead connect to your local node and get its information from there.

Since Bisq relies on BIP 37 which Bitcoin Core has turned off by default since 0.19.0, you will need to enable this feature by adding `peerbloomfilters=1` to your `bitcoin.conf` file. Otherwise Bisq will be unable to receive Bitcoin transactions. This is likely the syncing issues you are running into.

For some more information about local node settings in Bisq, you can read <https://bisq.wiki/Connecting_to_your_own_Bitcoin_node>.

> **Comments:**
> **username_0**: Can I ask why exactly Bisq would be relying on some weird Google-made BIP from 2012 when even Bitcoin Core has (apparently) rejected it?  
> **username_1**: The BIP was made by a person who was working at Google at that time, but it is not a Google made BIP. BIP 37 was the primary way to implement SPV and Bitcoin Core implemented it for a long time. However there are alternative SPV methods now such as BIP 157/158, but many older software still rely on BIP 37.  
> **username_2**: Is there some security risk on enabling this flag in bitcoin node? (https://github.com/bitcoin/bitcoin/issues/9540)  

---

