-
Notifications
You must be signed in to change notification settings - Fork 13
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
Not able to get any connection - Windows QT #13
Comments
The IP addresses listed in the log file are antique and no longer resolve to Slimcoin nodes. Adding at least one resolving address would enable your Slimcoin node (or "wallet" as many call it) to connect to the other nodes comprising the Slimcoin network. As with all other Bitcoin clones, Slimcoin has one or more IP addresses hard-coded in the source, listed as "DNS seeds". Here is the corresponding section of the Slimcoin cient code (
It is purely convention is that the "DNS seed" IP addresses should resolve to a "list of seed addresses". Currently, no-one has chosen to provide the Slimcoin network with such a service, so the original, antique, non-resolving-and-therefore-useless IP address of This is why all new Slimcoin client operators explicitly need to configure a list of IP addresses of nodes on the Slimcoin network in the
Perhaps we might rephrase this issue as "Ensure DNS seeds resolve". |
Thank you very much. But how as 0815-user should you know where to find that IP-adresses? |
Just ask around or check the block explorer. Or you could maintain a permanent node over a long period of time and establish a long-lasting IP address that is worth the effort of hard-coding in the source. Few people can manage this, so any IP addresses that are hard-coded eventually fail to resolve. |
Updating node list will be today, when I get them |
I just newly downloaded the Windows QT and startet it. I tried it even with admin rights, but it can't establish any connection. I've even run this for days and it won't connect to any server in slimcoin network.
Here the logfile:
The text was updated successfully, but these errors were encountered: