Connecting to your own Bitcoin node - Revision history

SuddenWhipVapor: /* General node settings */

2026-09-19T08:03:41Z

General node settings

SuddenWhipVapor: /* General node settings */

2026-09-19T08:02:43Z

General node settings

SuddenWhipVapor: /* General node settings */

2026-09-19T08:01:23Z

General node settings

SuddenWhipVapor: /* General node settings */

2026-09-19T08:01:04Z

General node settings

SuddenWhipVapor: /* General node settings */

2026-09-19T07:45:00Z

General node settings

SuddenWhipVapor: /* Connecting to another Bitcoin node */

2026-05-26T21:30:28Z

Connecting to another Bitcoin node

Strayorigin: clean up code section for easy copy

2026-05-03T17:36:02Z

clean up code section for easy copy

SuddenWhipVapor: /* Troubleshooting */

2025-05-22T18:21:00Z

Troubleshooting

SuddenWhipVapor: /* Troubleshooting */

2025-05-22T18:20:42Z

Troubleshooting

SuddenWhipVapor: /* Troubleshooting */

2025-05-22T18:20:01Z

Troubleshooting

@@ Line 20: / Line 20: @@
 * disables the pruning of old blocks
 * allows Bisq to run its SPV wallet
-* prevents Bisq from repeatedly losing connection to your node in case your wallet history has many transactions
+* prevents Bisq from repeatedly losing connection to your node in case your wallet history has many transactions, by limiting the tx retention in the local mempool to 24hrs
 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.

@@ Line 16: / Line 16: @@
 </pre>
-* '''server=1''': enables the block server mode
+which in turn:
-* '''prune=0''': disables the pruning of old blocks
+* enables the block server mode
-* '''peerbloomfilters=1''': allows Bisq to run its SPV wallet
+* disables the pruning of old blocks
-* '''mempoolexpiry=24''': prevents Bisq from repeatedly losing connection to your node in case your wallet history has many transactions
+* allows 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.

@@ Line 19: / Line 19: @@
 * '''prune=0''': disables the pruning of old blocks
 * '''peerbloomfilters=1''': allows Bisq to run its SPV wallet
-* '''mempoolexpiry=1''': prevents Bisq from repeatedly losing connection to your node in case your wallet history has many transactions
+* '''mempoolexpiry=24''': prevents Bisq from repeatedly losing connection to your node in case your wallet history has many transactions
 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.

@@ Line 13: / Line 13: @@
 prune=0
 peerbloomfilters=1
-mempoolexpiry=1
+mempoolexpiry=24
 </pre>

@@ Line 13: / Line 13: @@
 prune=0
 peerbloomfilters=1
 </pre>
@@ Line 18: / Line 19: @@
 * '''prune=0''': disables the pruning of old blocks
 * '''peerbloomfilters=1''': allows 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.

@@ Line 36: / Line 36: @@
 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 this line in bitcoin.conf: <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 7: / Line 7: @@
 = General node settings =
-The bitcoin.conf file needs to contain the following settings (either by adding them or editing the existing ones):
+The <code>bitcoin.conf</code> file needs to contain the following settings. You can copy and paste this block directly into your configuration file:
-<code>server=1</code><br>
+<pre>
-<code>prune=0</code><br>
+server=1
-<code>peerbloomfilters=1</code><br>
+prune=0
-which in turn:
+* '''server=1''': enables the block server mode
-* enable the block server mode
+* '''prune=0''': disables the pruning of old blocks
-* disable the pruning of old blocks
+* '''peerbloomfilters=1''': allows 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.
@@ Line 28: / Line 29: @@
 = Connecting to another Bitcoin node =
-By default, Bisq maximizes your privacy by connecting to nodes run by trusted  Bisq contributors.
+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 <code>Settings</code> > <code>Network Info</code>. Bisq will validate the address and connect to the specified node the next time it starts.
@@ Line 38: / Line 39: @@
 * 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
 = 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:
- <code>/Applications/Bisq.app/Contents/MacOs/Bisq -btcNodes=ybryiy2k4p4pery4qseap4iu2rxput2akuvpvczwvg4eyfafcdsvyqid.onion:8333 -useTorForBtc=true </code>
+<pre>
 /Applications/Bisq.app/Contents/MacOs/Bisq -btcNodes=ybryiy2k4p4pery4qseap4iu2rxput2akuvpvczwvg4eyfafcdsvyqid.onion:8333 -useTorForBtc=true
 For Linux:
+<pre>
- <code>/opt/bisq/bin/Bisq -btcNodes=ybryiy2k4p4pery4qseap4iu2rxput2akuvpvczwvg4eyfafcdsvyqid.onion:8333 -useTorForBtc=true </code>
+/opt/bisq/bin/Bisq -btcNodes=ybryiy2k4p4pery4qseap4iu2rxput2akuvpvczwvg4eyfafcdsvyqid.onion:8333 -useTorForBtc=true
 For Windows:
+<pre>
- <code>%localappdata%\Bisq\Bisq.exe -btcNodes=ybryiy2k4p4pery4qseap4iu2rxput2akuvpvczwvg4eyfafcdsvyqid.onion:8333 -useTorForBtc=true </code>
+%localappdata%\Bisq\Bisq.exe -btcNodes=ybryiy2k4p4pery4qseap4iu2rxput2akuvpvczwvg4eyfafcdsvyqid.onion:8333 -useTorForBtc=true
+</pre>
 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".

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