Enable 'peerbloomfilters' option on localnet bitcoind

Problem: Bitcoind Core v0.90.0 changed the default value of its
'peerbloomfilters' option from 1 to 0, now disabling them by default.
Bisq requires bloom filters be enabled on the Bitcoin node(s) it
communicates with, so users who are running >= v0.90 would get errors
when attempting to run `make bitcoind` with that target's current
recipe.

Solution: This change explicitly sets the 'peerbloomfilters' option to
1, ensuring it is enabled in any case. Note that this option has existed
in Bitcoin Core since v0.12.0, so there is no real concern for this new
option breaking users that are still on 0.18.x or even much earlier.
This commit is contained in:
Chris Beams 2019-12-02 20:18:38 +01:00
parent 5fb4b2156c
commit eb2d6b3992
No known key found for this signature in database
GPG Key ID: 3D214F8F5BC5ED73

View File

@ -164,6 +164,7 @@ bitcoind: .localnet
-regtest \ -regtest \
-prune=0 \ -prune=0 \
-txindex=1 \ -txindex=1 \
-peerbloomfilters=1 \
-server \ -server \
-rpcuser=bisqdao \ -rpcuser=bisqdao \
-rpcpassword=bsq \ -rpcpassword=bsq \