Difference between revisions of "Connecting to your own Bitcoin node"
Plebeian9000 (talk | contribs) (add initial page on connecting bisq to specific bitcoin node) |
Plebeian9000 (talk | contribs) m |
||
| Line 10: | Line 10: | ||
Other requirements: | Other requirements: | ||
| − | * Specify <code>peerbloomfilters=1</code> in your <code> | + | * Specify <code>peerbloomfilters=1</code> in your <code>bitcoin.conf</code> file if running 0.19.0.1 or later |
* Make sure your node is not running in pruned mode | * Make sure your node is not running in pruned mode | ||
Revision as of 16:12, 17 August 2020
Bisq will connect to your local Bitcoin node if it finds it upon starting up. This article contains the requirements for this to work correctly.
You can also specify the addresses of particular Bitcoin nodes in Settings > Network Info.
Connecting to a local Bitcoin node
If you're running a Bitcoin full node on the same machine as Bisq, Bisq should connect to your node on startup—it will look for Bitcoin Core or bitcoind running on localhost on port 8333.
Other requirements:
- Specify
peerbloomfilters=1in yourbitcoin.conffile if running 0.19.0.1 or later - Make sure your node is not running in pruned mode
Connecting to another Bitcoin node
By default, Bisq maximizes your privacy by connecting to nodes run by trusted Bisq contributors.
If you'd like to connect to another node, you can specify its address in Settings > Network Info. Bisq will make sure it can connect to the node to validate the address, and connect to that node the next time it starts.
