There is an issue with IRC peer discovery in version 3.24.60. Current system randomly sends clients to #namecoin0 to #namecoin99, but there are not enough active users on the network to support so many channels. Thus, many folks are reporting being unable to get any connections at startup.
zamgo wrote:There is an issue with IRC peer discovery in version 3.24.60. Current system randomly sends clients to #namecoin0 to #namecoin99, but there are not enough active users on the network to support so many channels. Thus, many folks are reporting being unable to get any connections at startup.
note: quick workaround now is to use -addnode to get your first connection.
Might make sense to change it to GetRandInt(10) or similar. Though the dns seeding should still let you find nodes even without the -addnode being used, or is that not set up for namecoins?
Thank you for raising this issue. I was already wondering why I sometimes wait long time for connections after restart of namecoind. But I guess that explains. As a quick workaraund we should gather the pool IP addresses or other well connected 24/7 namecoin nodes. Users can then add them to their bitcoin.conf.
If I remember correctly we had a few (two?) nodes hardcoded into the client. Are they still online? Is there a possibility to add some nodes to all IRC channels or just spread enough?
zamgo wrote:There is an issue with IRC peer discovery in version 3.24.60. Current system randomly sends clients to #namecoin0 to #namecoin99, but there are not enough active users on the network to support so many channels. Thus, many folks are reporting being unable to get any connections at startup.