Supported Feathercoin client versions: Current production Version: 0.16.0.
Old Production Version: 0.13.2
Info: If you have problems to post, create one post in the ‘newbies’ category and try again. If you have further problems, find support under Guides or use the shoutbox
Online list of active p2pool nodes available
It’s maintained by me.
It is more or less a crawler running on nodejs, that uses the peer list of an initial specified p2pool node to determine the active p2pool nodes.
The code can be found at https://github.com/wellenreiter01/p2pool-scanner-neoscrypt
There is no manual ‘adding’ of nodes, as every node that is part of the p2pool cloud and has the interface running on the default tcp port (19327) is added to the list.
Have you got “issues” set off in Github on the pool scanner? I noticed there was no feathercoin.png in resources and was going to raise an issue, before seeing if it’s easy to fix?
Also, would be interesting to create an IP list, that we could then run through a script for further analysis. I sort of failed with nslookup, I was trying to do for FTCForumTools - but it could be Text" replaced with ping, or some / various other appropriate IP analysis tools?
usage : sudo ./IPBlocklist-nslookup -type=ns.sh >> nslookup -type=ns.out
rm nslookup -type=ns.out
nslookup -type=ns XXX.93.26.10
nslookup -type=ns XXX.93.34.214
nslookup -type=ns XXX.215.253.186
nslookup -type=ns XXX.227.1.237
the feathercoin.png and phoenixcoin.png are in the dev-branch
will be available at next merge
not sure if I understand the nslookup stuff
Wow, quick work on the fixes …
About creating a text list of IPs : if the p2pool scanner can produce a IP list, then that could be run as a script to ping the IPs or give other information (like I was trying to do with a nslookup script). …
That is : instead of adding a ping functionality in the code itself, create a list which can be run as a script to do ping or some other task on each IP…
It looked a bit weird because the MD interferes with Bash ! “#”
I’ve seen the site, I think.
they show only pools in a radius of < 120000 km from your detected location, but still I don’t see all sites I’d expect.
I’m not sure how they worked around that problem.
Just found a js snipplet implementing a kind of ping.
I will try to implement that for the scanner code
@Wellenreiter Site seems to be down?
it looks like a script stopped working.
Will fix it today
The scanner had lost all nodes. Not sure why…