Difference between revisions of "Connecting to your own Bitcoin node"
Plebeian9000 (talk | contribs) (remove general node configuration requirements, to be placed in another section) |
Plebeian9000 (talk | contribs) (add note on connecting to bitcoind 0.21 over tor) |
||
| Line 4: | Line 4: | ||
__TOC__ | __TOC__ | ||
| + | |||
| + | = General node settings = | ||
| + | |||
| + | Make sure the node you're looking to connect to, whether local or remote, meets the following requirements: | ||
| + | * Specify <code>peerbloomfilters=1</code> in your <code>bitcoin.conf</code> file if running 0.19.0.1 or later | ||
| + | * Make sure node is ''not'' running in pruned mode (<code>pruned=N</code> in config means node is pruning blocks) | ||
= Connecting to a local Bitcoin node = | = Connecting to a local Bitcoin node = | ||
| Line 16: | Line 22: | ||
If you'd like to connect to another node, you can specify its address in <code>Settings</code> > <code>Network Info</code>. Bisq will validate the address and connect to the specified node the next time it starts. | If you'd like to connect to another node, you can specify its address in <code>Settings</code> > <code>Network Info</code>. Bisq will validate the address and connect to the specified node the next time it starts. | ||
| + | |||
| + | As of this writing, Bisq cannot connect to Bitcoin nodes with Tor v3 addresses. | ||
| + | |||
| + | If you're having issues connecting to a Bitcoin node running 0.21 or later over Tor, consider following the following instructions from [https://bitcoincore.org/en/releases/0.21.0/ the Bitcoin Core release notes] to downgrade your node to Tor v2. | ||
| + | |||
| + | <blockquote> | ||
| + | The Tor onion service that is automatically created by setting the <code>-listenonion</code> configuration parameter will now be created as a Tor v3 service instead of Tor v2. The private key that was used for Tor v2 (if any) will be left untouched in the <code>onion_private_key</code> file in the data directory (see <code>-datadir</code>) and can be removed if not needed. Bitcoin Core will no longer attempt to read it. The private key for the Tor v3 service will be saved in a file named <code>onion_v3_private_key</code>. To use the deprecated Tor v2 service (not recommended), the <code>onion_private_key</code> can be copied over <code>onion_v3_private_key</code>, e.g. <code>cp -f onion_private_key onion_v3_private_key</code>. | ||
| + | </blockquote> | ||
| + | |||
| + | Bisq relies on [https://bitcoinj.org/ bitcoinj] to interact with Bitcoin nodes, and bitcoinj has not integrated support for Tor v3 addresses yet. We're [https://github.com/bitcoinj/bitcoinj/issues/2067 working with them to do it], however, and will update the community (and this article) when it's ready. | ||
Revision as of 19:43, 10 February 2021
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.
Contents
General node settings
Make sure the node you're looking to connect to, whether local or remote, meets the following requirements:
- Specify
peerbloomfilters=1in yourbitcoin.conffile if running 0.19.0.1 or later - Make sure node is not running in pruned mode (
pruned=Nin config means node is pruning blocks)
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.
Just make sure to not be running any other 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.
As of this writing, Bisq cannot connect to Bitcoin nodes with Tor v3 addresses.
If you're having issues connecting to a Bitcoin node running 0.21 or later over Tor, consider following the following instructions from the Bitcoin Core release notes to downgrade your node to Tor v2.
The Tor onion service that is automatically created by setting the
-listenonionconfiguration parameter will now be created as a Tor v3 service instead of Tor v2. The private key that was used for Tor v2 (if any) will be left untouched in theonion_private_keyfile in the data directory (see-datadir) and can be removed if not needed. Bitcoin Core will no longer attempt to read it. The private key for the Tor v3 service will be saved in a file namedonion_v3_private_key. To use the deprecated Tor v2 service (not recommended), theonion_private_keycan be copied overonion_v3_private_key, e.g.cp -f onion_private_key onion_v3_private_key.
Bisq relies on bitcoinj to interact with Bitcoin nodes, and bitcoinj has not integrated support for Tor v3 addresses yet. We're working with them to do it, however, and will update the community (and this article) when it's ready.
