Replace v3 onion bootstrap seeds with valid Namecoin full nodes #495
Conversation
|
@JeremyRand what do you think about this change? I believe you updated the seed nodes list last (but maybe I misremember). |
|
@JeremyRand This makes sense yes, you are correct. Addressed in 644e79f |
The way I see that list has been updated by @JeremyRand recently (December 2021) and while of course no node is guaranteed to be stable all the time there are plenty of node addresses there and a big % should work. I can open a PR for that as well and put all the IP addresses reported by my dnsseeds, if you think it's useful. |
|
ACK 319b0a5 |
|
ACK from me as well. @ss11s Please squash all commits into a single one, then we can merge it. |
Fix the additional leading empty spaces, reverse to the original date and added TODO lines so it's clear that these networks are supported and stable nodes there are welcomed. Replace with valid Namecoin full nodes Some manually added reliable v3 onion NMC full nodes to help initial Tor bootstrapping. Add comments for i2p and cjdns as they are supported Allowing these comments as suggested, so it's known that i2p and cjdns networks are supported as well, so peers can/could be in these networks as well. Fix typo Fix date typo.
|
@domob1812 done. sorry for delay. |
|
Thanks. Please resolve the conflicts as well. Also - I've myself so far only worked with the |
|
@domob1812 done. is there any other place we need to replace BTC nodes with valid NMC nodes? By looking at our upstream I only identified this file. |
|
@domob1812 is there anything more we need to do here? Getting back on this as I recently got an email from an user that was unable to bootstrap to the network with a node used in |
Some manually added reliable v3 onion Namecoin MainNet full nodes to help initial Tor bootstrapping.