Connecting to your own Bitcoin node - Revision history

SuddenWhipVapor: /* Troubleshooting */

2025-05-22T18:21:00Z

Troubleshooting

2025-05-22T18:20:42Z

Troubleshooting

2025-05-22T18:20:01Z

Troubleshooting

2025-02-06T14:28:20Z

corrected code/missing "="

2024-11-20T15:41:09Z

Troubleshooting: remove reference to ronin dojo

2024-11-20T15:16:49Z

Troubleshooting: fix path to windows executable

2024-11-20T15:14:14Z

Troubleshooting: fix path to MacOS executable

2024-11-08T07:25:48Z

Troubleshooting: updated suggested node and feretated nodes link

2024-06-06T19:52:08Z

Troubleshooting

2023-11-27T10:53:59Z

General node settings

← Older revision		Revision as of 18:21, 22 May 2025
Line 57:		Line 57:


−	After Bisq successfully started and synchronized by running it with that command, you should then go to Settings > Network info, and select again "Use provided Bitcoin Core nodes"	+	After Bisq successfully started and synchronized by running it with that command, you should then go to Settings > Network info, and select again "Use provided Bitcoin Core nodes".
		+

	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].		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].

@@ Line 56: / Line 56: @@
   <code>%localappdata%\Bisq\Bisq.exe -btcNodes=ybryiy2k4p4pery4qseap4iu2rxput2akuvpvczwvg4eyfafcdsvyqid.onion:8333 -useTorForBtc=true </code>
-After Bisq successfully started and synchronized with this line, you should then go to Settings > Network info, and select again "Use provided Bitcoin Core nodes"
 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].

← Older revision		Revision as of 18:20, 22 May 2025
Line 55:		Line 55:

	<code>%localappdata%\Bisq\Bisq.exe -btcNodes=ybryiy2k4p4pery4qseap4iu2rxput2akuvpvczwvg4eyfafcdsvyqid.onion:8333 -useTorForBtc=true </code>		<code>%localappdata%\Bisq\Bisq.exe -btcNodes=ybryiy2k4p4pery4qseap4iu2rxput2akuvpvczwvg4eyfafcdsvyqid.onion:8333 -useTorForBtc=true </code>
		+
		+	After Bisq successfully started and synchronized with this line, you should then go to Settings > Network info, and select again "Use provided Bitcoin Core nodes"

	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].		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].

@@ Line 35: / Line 35: @@
 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 <code>0.0.0.0</code> rather than <code>127.0.0.1</code> (add a line that says <code>bind 0.0.0.0</code>)
+* have Bitcoin daemon listen to <code>0.0.0.0</code> rather than <code>127.0.0.1</code> (add a line that says <code>bind=0.0.0.0</code>)
 * uncheck "Use Tor for Bitcoin network" under Settings>Network in Bisq application
 * fill in your node's local network <code>ipaddress:8333</code> in "Use custom bitcoin Core nodes" field

@@ Line 43: / Line 43: @@
 = Troubleshooting =
-Most of the issues experienced by users come from trying to associate to a Ronin Dojo node, which often won't let Bisq connect a second time, if at all even the first; we are not aware of any reproducible solution to this, and suggest to use a different node distribution for Bisq.
+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:

@@ Line 48: / Line 48: @@
 For MacOS:
-  <code>Bisq -btcNodes=ybryiy2k4p4pery4qseap4iu2rxput2akuvpvczwvg4eyfafcdsvyqid.onion:8333 -useTorForBtc=true </code>
+  <code>/Applications/Bisq.app/Contents/MacOs/Bisq -btcNodes=ybryiy2k4p4pery4qseap4iu2rxput2akuvpvczwvg4eyfafcdsvyqid.onion:8333 -useTorForBtc=true </code>
 For Linux:

@@ Line 48: / Line 48: @@
 For MacOS:
-  <code>Bisq -btcNodes=devinbtctu7uctl7hly2juu3thbgeivfnvw3ckj3phy6nyvpnx66yeyd.onion:8333 -useTorForBtc=true </code>
+  <code>Bisq -btcNodes=ybryiy2k4p4pery4qseap4iu2rxput2akuvpvczwvg4eyfafcdsvyqid.onion:8333 -useTorForBtc=true </code>
 For Linux:
-  <code>/opt/bisq/bin/Bisq -btcNodes=devinbtctu7uctl7hly2juu3thbgeivfnvw3ckj3phy6nyvpnx66yeyd.onion:8333 -useTorForBtc=true </code>
+  <code>/opt/bisq/bin/Bisq -btcNodes=ybryiy2k4p4pery4qseap4iu2rxput2akuvpvczwvg4eyfafcdsvyqid.onion:8333 -useTorForBtc=true </code>
 For Windows:
-  <code>C:\Users\your-username-here\AppData\Local\Bisq\Bisq.exe -btcNodes=devinbtctu7uctl7hly2juu3thbgeivfnvw3ckj3phy6nyvpnx66yeyd.onion:8333 -useTorForBtc=true </code>
+  <code>C:\Users\your-username-here\AppData\Local\Bisq\Bisq.exe -btcNodes=ybryiy2k4p4pery4qseap4iu2rxput2akuvpvczwvg4eyfafcdsvyqid.onion:8333 -useTorForBtc=true </code>
-Contributor nodes can be seen [https://github.com/bisq-network/bisq/blob/7c07cdb6ff60ad1186dea33acdfb688668c2aae6/core/src/main/java/bisq/core/btc/nodes/BtcNodes.java#L51-L76 here in the Bisq code].
+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]].
 [[Command_line_options|More info on command line options]].

@@ Line 10: / Line 10: @@
 <code>server=1</code><br>
-<code>pruned=0</code><br>
+<code>prune=0</code><br>
 <code>peerbloomfilters=1</code><br>