As we can tell from the new Grin seed check report I’ve just put up, our seed nodes need to be updated, (particularly on testnet which is now invite-only due to there being no available seed nodes at all!)
So we clearly need some volunteers to host seed nodes! If you’re able and willing to take on the responsibility of keeping a node maintained, available and up to date, as well as able to configure a domain for it, please let me know on this thread, and I’ll get the list updated and merged before the next core release. Note that we need a domain or subdomain, not just an IP address.
I don’t think we need to put any restrictions on who can run a node or how many we take, we can take as many as we can get and the report will tell us if any fall into disrepair and need to be replaced.
The first changes are:
Mainnet
Remove mainnet.seed.grin.icu
Remove mainnet.seed.713.mw
I’ll be replacing grinseed.yeastplume.org with grinseed.revcore.net
Testnet
Remove floonet.seed.grin.icu
Remove floonet.seed.713.mw
floonet.seed.grin.lesceller.com and floonet.seed.grin.prokapi.com are currently unresponsive, but I know their owners are about so alert them and give them a chance to fix their testnet nodes. If that can’t happen, remove them.
Just have a reliable track record of keeping your nodes online.
And then do a PR on the GRIN github repository for your nodes to be added to the DNS-seed.
Can you unite all 3 IPs of your nodes under single A records like main-seed.grin.money and test-seed.grin.money, it will help if one of your VPS will become unavailable and can be added at grin seed list PR easily.
I contacted them all (for Mainnet) via email although trinitron’s domain/email server appears to be down. Lets see, indeed that is why we have this contact information. Kind of silly that we did not contact them earlier by email.
As ardocrat suggested me, you better to have 3 servers are running (on server can run both mainnet/testnet in parallel), and point your A records to 3 IPs.
