diff --git a/opsec/haveno-seednode/index.html b/opsec/haveno-seednode/index.html index 2b47387..3bfdc72 100644 --- a/opsec/haveno-seednode/index.html +++ b/opsec/haveno-seednode/index.html @@ -303,7 +303,7 @@ im6hcl7hknvsrsns2newv4orfv3kd2ly5yvqtbfkiyzoohscyp5htgqd.onion:2002(@anon6) tqxmkjprxry7xwf2sdvy55etnkp6eddc4uxj5fd6rwpnc472mpizgqyd.onion:2003(@nihilist1) -

Then we edit them accordingly by replacing "XMR_STAGENET" to "XMR_MAINNET", and by editing the xmrNode port to 18081 (the rpc bind port), and also edit the binary location:

+

Then we edit them accordingly by replacing "XMR_STAGENET" to "XMR_MAINNET", editing the xmrNode port to 18081 (the rpc bind port), edit the binary location, and also the user that is running the seed nodes (in my case it is the root user):


 [ Datura ] [ /dev/pts/10 ] [/srv/haveno-reto]
 → cat /etc/systemd/system/haveno-seednode.service
@@ -467,7 +467,7 @@ Oct 06 13:39:13 Datura Haveno-Seednode2[1412193]: Oct-06 13:39:13.059 [Connectio

Then haveno launches as intended, and when you check into the network tab, you can see that it is bootstraping using your 2 seednodes, instead of the default ones:

-

And from there, all you need to do is let the Haveno Network Administrators know that you are running some seed nodes. So as you need to reach out to the Reto network administrators, you can ping them on their SimpleX chatroom.

+

And from there, all you need to do is let the Haveno Network Administrators know that you are running some seed nodes. So as you need to reach out to the Reto network administrators, you can ping them on their SimpleX chatroom. From there you can ask them if they are willing to put your seed node in their repository, so that upon the next release, everyone that uses the Haveno Network will be able to use your 2 new nodes to bootstrap with.