Difference between revisions of "Connecting to your own Bitcoin node"
(→Troubleshooting: remove reference to ronin dojo) |
|||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | 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. | + | Bisq will '''connect to [[Installing_your_own_Bitcoin_node|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 <code>Settings</code> > <code>Network Info</code>. | You can also specify the addresses of particular Bitcoin nodes in <code>Settings</code> > <code>Network Info</code>. | ||
| Line 10: | Line 10: | ||
<code>server=1</code><br> | <code>server=1</code><br> | ||
| − | <code> | + | <code>prune=0</code><br> |
<code>peerbloomfilters=1</code><br> | <code>peerbloomfilters=1</code><br> | ||
| Line 43: | Line 43: | ||
= Troubleshooting = | = Troubleshooting = | ||
| − | + | If you get into a state where Bisq is unable to connect, or stuck at SPV resync on the loading screen, you can revert to a provided node as follows. | |
| − | |||
| − | If you get into a state where Bisq is unable to connect, you can revert to a provided node as follows. | ||
For MacOS: | For MacOS: | ||
| − | <code>Bisq -btcNodes= | + | <code>/Applications/Bisq.app/Contents/MacOs/Bisq -btcNodes=ybryiy2k4p4pery4qseap4iu2rxput2akuvpvczwvg4eyfafcdsvyqid.onion:8333 -useTorForBtc=true </code> |
For Linux: | For Linux: | ||
| − | <code>/opt/bisq/bin/Bisq -btcNodes= | + | <code>/opt/bisq/bin/Bisq -btcNodes=ybryiy2k4p4pery4qseap4iu2rxput2akuvpvczwvg4eyfafcdsvyqid.onion:8333 -useTorForBtc=true </code> |
For Windows: | For Windows: | ||
| − | <code> | + | <code>%localappdata%\Bisq\Bisq.exe -btcNodes=ybryiy2k4p4pery4qseap4iu2rxput2akuvpvczwvg4eyfafcdsvyqid.onion:8333 -useTorForBtc=true </code> |
| − | Contributor nodes can be seen [https://github.com/bisq-network/bisq/blob/ | + | Contributor nodes can be seen [https://github.com/bisq-network/bisq/blob/8d345000ee22350ff6d203d4dee8c52285b6d302/core/src/main/java/bisq/core/btc/nodes/BtcNodes.java#L51-L67 here in the Bisq code]. |
[[Running_from_the_command_line|More info on running from the command line]]. | [[Running_from_the_command_line|More info on running from the command line]]. | ||
[[Command_line_options|More info on command line options]]. | [[Command_line_options|More info on command line options]]. | ||
Latest revision as of 15:41, 20 November 2024
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
The bitcoin.conf file needs to contain the following settings (either by adding them or editing the existing ones):
server=1
prune=0
peerbloomfilters=1
which in turn:
- enable the block server mode
- disable the pruning of old blocks
- allow Bisq to run its SPV wallet
Multiple reports have been received, where any declination of the Ronin node just won't work, or will work once, only to stop working after the next reboot, requiring a restore to network provided nodes. We are not able to suggest a workaround, except involving Ronin support.
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.
Bisq supports connecting to Bitcoin nodes with Tor v3 addresses: this is the easiest path to take, since you only have to fill in your node's onion address in settings.
If your node is on your local network, connecting directly to it rather than using Tor would reduce latency by a sensible degree. In order to do this:
- make sure the node's firewall allows incoming connections on port 8333 from the local network
- have Bitcoin daemon listen to
0.0.0.0rather than127.0.0.1(add a line that saysbind 0.0.0.0) - uncheck "Use Tor for Bitcoin network" under Settings>Network in Bisq application
- fill in your node's local network
ipaddress:8333in "Use custom bitcoin Core nodes" field
Explaining in detail each step of the above goes past the scope of this guide, yet you can usually find more information either by searching for specific guides, or asking on discussion boards/groups.
Troubleshooting
If you get into a state where Bisq is unable to connect, or stuck at SPV resync on the loading screen, you can revert to a provided node as follows.
For MacOS:
/Applications/Bisq.app/Contents/MacOs/Bisq -btcNodes=ybryiy2k4p4pery4qseap4iu2rxput2akuvpvczwvg4eyfafcdsvyqid.onion:8333 -useTorForBtc=true
For Linux:
/opt/bisq/bin/Bisq -btcNodes=ybryiy2k4p4pery4qseap4iu2rxput2akuvpvczwvg4eyfafcdsvyqid.onion:8333 -useTorForBtc=true
For Windows:
%localappdata%\Bisq\Bisq.exe -btcNodes=ybryiy2k4p4pery4qseap4iu2rxput2akuvpvczwvg4eyfafcdsvyqid.onion:8333 -useTorForBtc=true
Contributor nodes can be seen here in the Bisq code.
