Updating seeds has been a pain point for releases for some time now.
In order to contribute to updating seeds reliably, a contributor must have
access to both mainnet and testnet seeders. This poses the following challenges:
- Contributors must be either:
a) A sysadmin with the skills to setup their own seeder(s), or
b) Given SSH access to a server by a sysadmin with the skills to setup their own seeder(s) and provide the appropriate security for a multi-user environment.
- The seeder(s) must be running for 2-4 weeks BEFORE updating seeds, making it difficult to pull in new contributors.
Adding this new script decouples the above problems from the process of updating the
seeds by providing a way for any contributor to update seeds without themselves needing
to setup seeders. This leaves 1.b for which I have setup seederdump.bitframe.org and
will provide (in the future) a script and setup instructions to easily replicate for
other server hosts for additional redundancy.