decred / dcrseeder Goto Github PK

View Code? Open in Web Editor NEW

11.0 9.0 10.0 105 KB

Decred Seeder

License: ISC License

Go 98.48% Shell 1.52%

decred bitcoin seeder dns cryptocurrency

dcrseeder's Introduction

dcrseeder

Overview

dcrseeder is a crawler for the Decred network, which exposes a list of reliable nodes via a built-in HTTP server.

When dcrseeder is started for the first time, it will connect to the dcrd node specified in config, send a getaddrs request, expecting an addr message response. This message contains hostnames and IPs of peers known by the node. dcrseeder will then connect to each of these peers, send a getaddrs request, and will continue traversing the network in this fashion. dcrseeder maintains a list of all known peers and periodically checks that they are online and available. The list is stored on disk in a json file, so on subsequent start ups the dcrd node specified in config does not need to be online.

When dcrseeder is queried for node information, it responds with details of a random selection of the reliable nodes it knows about.

Requirements

Go 1.20 or newer.

Getting Started

To build and install from a checked-out repo, run go install in the repo's root directory.

To start dcrseeder listening on localhost:8000 with an initial connection to working testnet node 192.168.0.1:

$ ./dcrseeder --testnet.enabled --testnet.seeder 192.168.0.1 --testnet.listen=localhost:8000

You will then need to redirect HTTPS traffic on your public IP to localhost:8000

An example configuration file lists the full set of options available.

Issue Tracker

The integrated github issue tracker is used for this project.

License

dcrseeder is licensed under the copyfree ISC License.

dcrseeder's People

Contributors

Stargazers

Watchers

Forkers

dajohi w1r2p1 romanornr viacoin jcvernaleo endurio chappjc peterzen jholdstock

dcrseeder's Issues

single process should be able to crawl and resolve multiple networks

Ideally a single dcrseeder process should be able to crawl both mainnet and testnet:

Specify one or two hostnames (one or both of mainnet and testnet)
Crawl one or both networks simultaneously
Launch a single DNS server that resolves one or more host names (two in the case of mainnet and testnet)

e.g.

Name server: ns.blah.org
Testnet host name: testnet-seed.blah.org (with NS record pointing to ns.blah.org)
Mainnet host name: mainnet-seed.blah.org (with NS record also pointing to ns.blah.org)

display statistics

perhaps a configuration option to display statistics every specified unit of time.

number of live nodes grouped by services
total number of live nodes:
number of IPs that still need checking:
number of dns lookups

etc...

Add IP sanity checks

IP addresses that are not publically routable should be ignored and never added to the cache.

ipv6 support

when exec dcrseeder -n seedserver.xxx.xxx -H mainnet-seed.xxx.xxx -l 2001:ac8:40:xxxx::xxxx:xxxx:53 -s 2001:ac8:40:xxxx::xxxx:xxxx
got a problem ResolveUDPAddr: address 2001:ac8:40:xxxx::xxxx:xxxx:53: no suitable address found
So now only support IPv4?

I do remember that the old seeder had a hardcoded list of all the other seeders:
https://github.com/decred/decred-seeder/blob/19351f3e3ec93b96ca3438c465c04163747d0c5c/main.cpp#L400
Did it use that to get the initial node list (assuming at least one of those must be up and possibly serving a static list of 'good' nodes, at least during the initial network bringup?

Regardless of the exact method, require a full node is a lot to ask for running a seeder (which is otherwise a very light task).