Difference between revisions of "Connecting to your own Bitcoin node"
Jump to navigation
Jump to search
Plebeian9000 (talk | contribs) m |
m (→Connecting to a local Bitcoin node: LTC incompatibility at startup.) |
||
| Line 12: | Line 12: | ||
* Specify <code>peerbloomfilters=1</code> in your <code>bitcoin.conf</code> file if running 0.19.0.1 or later | * 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 | ||
| + | * Don't run Bitcoin-based altcoin nodes (like LTC) while starting Bisq. | ||
= Connecting to another Bitcoin node = | = Connecting to another Bitcoin node = | ||
Revision as of 07:47, 19 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
- Don't run Bitcoin-based altcoin nodes (like LTC) while starting Bisq.
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 validate the address and connect to the specified node the next time it starts.
