-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add seed nodes domains #750
Comments
It might be better to use similar approach that is used for Bitcoin: https://developer.bitcoin.org/devguide/p2p_network.html#peer-discovery, example:
E.g. we will have the DNS |
yes, we can and certainly will use a atomicdex DNS seeder - however, we do not have such required implementation yet. Such a seeder implementation crawls the ADEX network and basically revisit seed nodes it has in the registry to ensure they still alive/up and also explore new ones to add to the list. BTC for example uses the one provided by sipa: https://github.com/sipa/bitcoin-seeder We can maybe add a |
are the IPs exchanged between the existing seed nodes? if so, we only need couple of working IPs in xxxx.seed.kmd.io to start with, all the others will then be exchanged |
Yes, the IPs are exchanged, but in current setup we have only 3 seed/bootstrap nodes which DNS have to be managed manually. The automated DNS seed seems to be not hard to implement and this approach will help to save our time on DNS management and speed up initial bootstrap because there will be more MM2 nodes addresses known immediately. |
Creating issue to not forget :)
domains are:
seed1.kmd.io
seed2.kmd.io
seed3.kmd.io
The text was updated successfully, but these errors were encountered: