Installing your own Bitcoin node - Revision history

Strayorigin: replaced references to retired btc node with a current one

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

2023-11-02T09:38:21Z

Setup the connection from Bisq to the node

2023-11-02T09:18:02Z

Connecting to a node on the same PC

2023-11-02T09:17:21Z

Connecting to a node on the same PC

2023-11-02T09:16:44Z

Setup the connection from Bisq to the node

@@ 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 48: / Line 48: @@
 <code>server=1</code><br>
-<code>pruned=0</code><br>
+<code>prune=0</code><br>
 <code>peerbloomfilters=1</code><br>

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

@@ Line 70: / Line 70: @@
 = Setup the connection from Bisq to the node =
-The following will change depending on where is located the node respectively to Bisq.
+The following will change depending on where the node is located respectively to Bisq.
 == Connecting to a node on the same PC ==

@@ Line 76: / Line 76: @@
 If the Bitcoin node is installed on the same machine as Bisq, the latter will automatically connect to it without the need to edit anything. Considering how Bisq will only run on amd64 architecture, you can achieve this with either your daily driver, or a dedicated laptop/desktop through direct or remote access (for example via [[Remote_control_via_web_browser_using_xpra|xpra]]).
-Just make sure to not be running any other Bitcoin-based altcoin nodes (like LTC) while starting Bisq.
+Make sure no other Bitcoin-based altcoin nodes (like LTC) are running while starting Bisq.
 == Connecting to a Bitcoin node on the same local network ==