Installing your own Bitcoin node - Revision history

SuddenWhipVapor: /* Setup the node to accept connections from Bisq */

2026-09-19T08:03:55Z

Setup the node to accept connections from Bisq

2026-09-19T08:02:11Z

Setup the node to accept connections from Bisq

2026-09-19T08:00:51Z

Setup the node to accept connections from Bisq

2026-09-19T07:46:46Z

Setup the node to accept connections from Bisq

2024-07-22T03:33:58Z

replaced references to retired btc node with a current one

2024-05-25T13:18:35Z

Hardware requirements

2023-11-27T10:52:54Z

Setup the node to accept connections from Bisq

2023-11-02T19:49:41Z

2023-11-02T09:42:09Z

Verify the connection

2023-11-02T09:39:59Z

Connecting to a remote node through the Tor Network

@@ Line 58: / Line 58: @@
 * disables the pruning of old blocks
 * allows Bisq to run SPV queries on the node
-* 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
 If the node is running on a separate machine, but on the same local network, it needs to listen for connections from external clients as well, and the easiest way of doing this is to add the following to the config file:

@@ Line 47: / Line 47: @@
 If you installed the client via command line interface following the guides linked above, you will probably have a working config file already, but in case you installed the GUI client, you will have to manually edit the <code>bitcoin.conf</code> file from within the settings, and make sure it contains the following:
-<code>server=1</code><br>
+<pre>
-<code>prune=0</code><br>
+server=1
-<code>peerbloomfilters=1</code><br>
+prune=0
-<code>mempoolexpiry=24</code><br>
+peerbloomfilters=1
 which in turn:

@@ Line 50: / Line 50: @@
 <code>prune=0</code><br>
 <code>peerbloomfilters=1</code><br>
-<code>mempoolexpiry=1</code><br>
+<code>mempoolexpiry=24</code><br>
 which in turn:

@@ Line 50: / Line 50: @@
 <code>prune=0</code><br>
 <code>peerbloomfilters=1</code><br>
 which in turn:
-* enable the block server mode
+* enables the block server mode
-* disable the pruning of old blocks
+* disables the pruning of old blocks
-* allow Bisq to run SPV queries on the node
+* allows Bisq to run SPV queries on the node
 If the node is running on a separate machine, but on the same local network, it needs to listen for connections from external clients as well, and the easiest way of doing this is to add the following to the config file:

@@ Line 107: / Line 107: @@
 For MacOS:
-  <code>Bisq -btcNodes=emzybtc3ewh7zihpkdvuwlgxrhzcxy2p5fvjggp7ngjbxcytxvt4rjid.onion:8333 -useTorForBtc=true </code>
+  <code>Bisq -btcNodes=devinbtctu7uctl7hly2juu3thbgeivfnvw3ckj3phy6nyvpnx66yeyd.onion:8333 -useTorForBtc=true </code>
 For Linux:
-  <code>/opt/bisq/bin/Bisq -btcNodes=emzybtc3ewh7zihpkdvuwlgxrhzcxy2p5fvjggp7ngjbxcytxvt4rjid.onion:8333 -useTorForBtc=true </code>
+  <code>/opt/bisq/bin/Bisq -btcNodes=devinbtctu7uctl7hly2juu3thbgeivfnvw3ckj3phy6nyvpnx66yeyd.onion:8333 -useTorForBtc=true </code>
 For Windows:
-  <code>C:\Users\your-username-here\AppData\Local\Bisq\Bisq.exe -btcNodes=emzybtc3ewh7zihpkdvuwlgxrhzcxy2p5fvjggp7ngjbxcytxvt4rjid.onion:8333 -useTorForBtc=true </code>
+  <code>C:\Users\your-username-here\AppData\Local\Bisq\Bisq.exe -btcNodes=devinbtctu7uctl7hly2juu3thbgeivfnvw3ckj3phy6nyvpnx66yeyd.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 in the Bisq code].

@@ Line 5: / Line 5: @@
 = Hardware requirements =
-The most demanding part of a full Bitcoin node is disk space: 1TB is considered the bare minimum, and a SSD is recommended, as the constant write operations would risk damaging the average mechanical disk. There are pruned nodes that will only keep the very last blocks of the blockchain in order to save on disk space, but as Bisq needs a fully verifying node, we will only be examining this case in the present guide.
+The most demanding part of a full Bitcoin node is disk space: 1TB is considered the bare minimum (2TB is better for future proofing your node), and a SSD is recommended, as the constant write operations would risk damaging the average mechanical disk. There are pruned nodes that will only keep the very last blocks of the blockchain in order to save on disk space, but as Bisq needs a fully verifying node, we will only be examining this case in the present guide.
 The following are viable hardware options to host the node:

@@ Line 8: / Line 8: @@
 The following are viable hardware options to host the node:
 * dedicated Raspberry Pi 3
 ** pros: very small, low power, completely silent
-** cons: no builtin display, keyboard nor storage, needs more initial maintenance
+** cons: no builtin display, keyboard nor storage, very low performance, needs more initial maintenance
 * your daily driver machine
 ** pros: no need to source additional hardware (except the additional storage if it's not enough), will likely not suffer from the limited additional overhead of a Bitcoin node while you use it normally

@@ Line 100: / Line 100: @@
 = Verify the connection =
-Once you connect to your own node, Bisq will use only that one to bridge to the bitcoin network, so you will see, in the bottom right corner of the application, that there is just one bitcoin network peer, and under Settings > Network you will notice that same node is the only ones listed among the ones you are connected to.
+Once you connect to your own node, Bisq will show <code>Bitcoin network peers: 1</code> in the bottom right corner, and under Settings > Network you will notice the node is the only one listed under "Bitcoin network".
 = Troubleshooting =

@@ Line 94: / Line 94: @@
 <code>bitcoin-cli getnetworkinfo | grep address.*onion</code>
-to obtain your onion address, copy it to the clipboard and paste it under Settings > Network > Use Custom Bitcoin Core nodes
+to obtain your onion address, copy it to the clipboard and paste it in Bisq under Settings > Network > Use Custom Bitcoin Core nodes
 Bisq will offer to restart, thus connecting to the custom remote node.