Manually select seednodes - Revision history

SuddenWhipVapor at 08:18, 22 June 2024

2024-06-22T08:18:18Z

Strayorigin: changed -seednode to -seedNodes as that is correct

2024-06-17T15:05:12Z

changed -seednode to -seedNodes as that is correct

Jmacxx at 15:36, 27 November 2023

2023-11-27T15:36:56Z

W000000t at 17:51, 29 June 2022

2022-06-29T17:51:36Z

W000000t at 17:51, 29 June 2022

2022-06-29T17:51:13Z

W000000t: Created page with "If Tor network is experiencing issues, and seednodes are only partially operational, leading to frequent inability to connect to the p2p network, the following method is one w..."

2022-06-29T17:24:39Z

Created page with "If Tor network is experiencing issues, and seednodes are only partially operational, leading to frequent inability to connect to the p2p network, the following method is one w..."

New page

If Tor network is experiencing issues, and seednodes are only partially operational, leading to frequent inability to connect to the p2p network, the following method is one workaround that will increase your probability of correctly running Bisq.

We want to manually connect to seednodes that appear to be working, rather than having Bisq randomly choose them; reach the network monitors available at the following addresses (click ''Continue'' in case your browser complains about the security of the page, they are just showing a large HTML table):
- http://46.101.179.224:8080/
- http://135.181.92.87:8080/

What you are looking for is in the '''Data inventory''' and '''DAO data''' columns, where you need to make sure that the former reports ''Number of Mediator: 2'' (do not mind skull and warning icons), and the latter shows a large number near ''Number of BSQ blocks'' (''171131'' at the time of writing).

During high network instability, only a handful of seednodes will show such requirements, and the data will also change both with time, and between the two monitor URLs, so your job is to identify those (at least a couple, the more the merrier) that show most consistently stable over time on all monitors, and note down their ''Node address:'' under the '''Seed node info''' column.

Once you have copied those <code>address.onion:port</code> strings, place them in a command line to start Bisq, appending them as a comma-separated list to the <code>-seednodes=</code> option, like so for example (for Linux):

<code>/opt/bisq/bin/Bisq -seedNodes=address1.onion:8000,address2.onion:8000,address3.onion:8000</code>

Press Enter, cross your fingers, and watch the magic happen (maybe), otherwise go back to square one and retry with different seednodes.

← Older revision		Revision as of 08:18, 22 June 2024
Line 1:		Line 1:
−	~~If Tor network~~ is experiencing issues, and seednodes are only partially operational, leading to frequent inability to connect to the p2p network, the following method is one workaround that will increase your probability of correctly running Bisq.	+	The monitor service is in the process of being transferred to a new operator, and is momentarily unavailable.<br>
−		+	This page will be restored as soon as a public node monitoring service is back up online.
−	~~We want to manually connect to seednodes that appear to be working, rather than having Bisq randomly choose them; reach the network monitors available at the following addresses (click ''Continue''~~ in ~~case your browser complains about~~ the ~~security~~ of ~~the page, they are just showing a large HTML table):~~
−	~~- http://5.189.155.112:8080/~~
−
−	~~What you are looking for is in the '''Data inventory''' and '''DAO data''' columns, where you need~~ to make sure that the former reports ''Number of Mediator: 2'' (do not mind skull and warning icons), and the latter shows a large integer near ''Number of BSQ blocks'' (''171131'' at the time of writing).
−
−	~~During high network instability, only~~ a ~~handful of seednodes will satisfy such requirements, and the data will also change both with time~~, and ~~between the two monitor URLs, so your job~~ is ~~to identify those (at least a couple, the more the merrier) that show most consistently stable over time on all monitors, and note down their ''Node address:'' under the '''Seed node info''' column~~.
−
−	~~Once you have copied those~~ <~~code~~>~~address.onion:port</code> strings, place them in a command line to start Bisq, appending them~~ as a ~~comma-separated list to the <code>-seedNodes=</code> option, like so for example (for Linux):~~
−
−	~~<code>/opt/bisq/bin/Bisq -seedNodes=address1.onion:8000,address2.onion:8000,address3.onion:8000</code>~~
−
−	~~Press Enter, cross your fingers, and watch the magic happen (maybe), otherwise go~~ back ~~to square one and retry with different seednodes~~.

@@ Line 2: / Line 2: @@
 We want to manually connect to seednodes that appear to be working, rather than having Bisq randomly choose them; reach the network monitors available at the following addresses (click ''Continue'' in case your browser complains about the security of the page, they are just showing a large HTML table):
-  - http://46.101.179.224:8080/
+  - http://5.189.155.112:8080/
 What you are looking for is in the '''Data inventory''' and '''DAO data''' columns, where you need to make sure that the former reports ''Number of Mediator: 2'' (do not mind skull and warning icons), and the latter shows a large integer near ''Number of BSQ blocks'' (''171131'' at the time of writing).

@@ Line 7: / Line 7: @@
 What you are looking for is in the '''Data inventory''' and '''DAO data''' columns, where you need to make sure that the former reports ''Number of Mediator: 2'' (do not mind skull and warning icons), and the latter shows a large integer near ''Number of BSQ blocks'' (''171131'' at the time of writing).
-During high network instability, only a handful of seednodes will show such requirements, and the data will also change both with time, and between the two monitor URLs, so your job is to identify those (at least a couple, the more the merrier) that show most consistently stable over time on all monitors, and note down their ''Node address:'' under the '''Seed node info''' column.
+During high network instability, only a handful of seednodes will satisfy such requirements, and the data will also change both with time, and between the two monitor URLs, so your job is to identify those (at least a couple, the more the merrier) that show most consistently stable over time on all monitors, and note down their ''Node address:'' under the '''Seed node info''' column.
 Once you have copied those <code>address.onion:port</code> strings, place them in a command line to start Bisq, appending them as a comma-separated list to the <code>-seednodes=</code> option, like so for example (for Linux):

@@ Line 8: / Line 8: @@
 During high network instability, only a handful of seednodes will satisfy such requirements, and the data will also change both with time, and between the two monitor URLs, so your job is to identify those (at least a couple, the more the merrier) that show most consistently stable over time on all monitors, and note down their ''Node address:'' under the '''Seed node info''' column.
-Once you have copied those <code>address.onion:port</code> strings, place them in a command line to start Bisq, appending them as a comma-separated list to the <code>-seednodes=</code> option, like so for example (for Linux):
+Once you have copied those <code>address.onion:port</code> strings, place them in a command line to start Bisq, appending them as a comma-separated list to the <code>-seedNodes=</code> option, like so for example (for Linux):
 <code>/opt/bisq/bin/Bisq -seedNodes=address1.onion:8000,address2.onion:8000,address3.onion:8000</code>
 Press Enter, cross your fingers, and watch the magic happen (maybe), otherwise go back to square one and retry with different seednodes.

@@ Line 5: / Line 5: @@
   - http://135.181.92.87:8080/
-What you are looking for is in the '''Data inventory''' and '''DAO data''' columns, where you need to make sure that the former reports ''Number of Mediator: 2'' (do not mind skull and warning icons), and the latter shows a large number near ''Number of BSQ blocks'' (''171131'' at the time of writing).
+What you are looking for is in the '''Data inventory''' and '''DAO data''' columns, where you need to make sure that the former reports ''Number of Mediator: 2'' (do not mind skull and warning icons), and the latter shows a large integer near ''Number of BSQ blocks'' (''171131'' at the time of writing).
 During high network instability, only a handful of seednodes will show such requirements, and the data will also change both with time, and between the two monitor URLs, so your job is to identify those (at least a couple, the more the merrier) that show most consistently stable over time on all monitors, and note down their ''Node address:'' under the '''Seed node info''' column.