I thought there was already a topic somewhere, but did not find it - so opening a new one. Besides the DNS seeds (of which we now fortunately already have a few for Namecoin Core!), Bitcoin also has hardcoded seed nodes as final fallback. They are necessary for Tor-only clients, since DNS seeds don't work over Tor. (The alternative is manually using -addnode or -connect.)
I think that Bitcoin generates the list by querying a DNS seed, at least "mostly" (but I don't know the precise way). I don't really see a lot of harm a bad node on the list could do, besides what someone trying to Sybil-attack the network could do anyway; but maybe I'm missing something.
Nevertheless, I suggest the following:
- I use the most stable nodes my seeder sees and add them as hardcoded IPv4 addresses.
- In addition, I know two .onion addresses of nodes that can be added as well. One is run by myself and the other by someone who volunteered to do so a few months ago.
Are there any objections to doing so? If someone wants to run dedicated stable seed nodes either as hidden service or with a fixed IP address, feel free to mention that here or in a future Github pull request and I will add them as well.
KsPZ5cWk2kXssD8p8ES1qffGUCm | NMC: NCdomob
Use your Namecoin identity as OpenID: https://nameid.org/