FTC p2pool public node list
-
Any chances to determine the pool names?
Would be more descriptive.
-
Missing FTCPool.ca 108.161.129.79
-
You asked for it. You get it. Pool names (Reverse lookup added). List is being generated again so it takes some time until all p2pools that are publically accessible (On Port 19327) are listed again. Let me know if you spot any issues.
Regards,
MrSheep -
Great work :)
I played around with the pool scanner myself a bit, but as I have no experience with server side javscript, I gave up after a short time ;)
-
Unfortunally reverse lookup won’t work many times because most servers are vhosted anyway so you’ll get the host/servername and not the vhostname.
One solution might be to have a separate vhostname-ipnumber list and associate that with the found ip numbers.
-
I can put in some static reverse lookups, if you wish. Any wishes? Yours (Prensel, the dutch one?) does not seem to be looked up correctly for example!?
-
best would be to modify the p2pool-api and include the local hostname there.
the $_server variable could probablay be used for that.
any customization of the node scanner can solve the problem for a given server only.see: [url=http://php.net/manual/de/reserved.variables.server.php]http://php.net/manual/de/reserved.variables.server.php[/url]
-
p2pool is python which is not my most liked language… ;-)
For now i have made the reverse lookup a bit less strict. However, it will then also do reverse lookups for hosts which have no forward DNS entry (like debbie.reho.nl). I may revert that change as you cannot reach the p2pool via the name in that case.
As long as i think about it, i have also added the link to the IP address to the p2pools list.
Regards,
MrSheep -
ftcpool.nl is vhosted on debbie.reho.nl
-
@prensel: But the reverse lookup says so for 141.138.141.253. I have reverted the change and only list host names for matching forward and reverse lookups. That seems to be more safe to me.
Any other feature requests?
MrSheep
-
Looks like it isn’t working, look at [url=http://pool2:19327/static/]http://pool2:19327/static/[/url] thats not gonna work :p
-
Yeah, that’s the backup pool for pool.maeh.org. As the script is currently running on that pool it does not add the domain name correctly. Fixed.
-
Nice! Now more people got to use p2pool :-\
-
If I look at the list it seems the p2pool network consist of just 10 really active nodes, is that true ?
It appears that i’m taking ‘care’ of almost 25% of the p2pool network capacity, we need some more hashing power here folks ! -
Yeah. It is a bit misleading as some pools that are still running the old version or on a different port (p2pool.org) are not in the list so far. But yes, we do need more active nodes and more hashing power. We started from 0 MH/s though…
-
I noticed, that some pools haven’t been seen for a couple of days.
After which time these pools are deleted?
A typical reason for a pool showing up only one day is, that he pool is using a DSL line and receives a new IP address every 24 hours.
-
Added that. Pools not answering for 1 hour are now being deleted from the list. They will be re-added once they’re active again and show up for the p2pool node (if they change ip address)
-
Is there any chance to determine what coin a pool is mining?
I cloned the p2pool-scanner from github to add an interactive pie chart, and my node-list shows
pool.ishtar.ca:19327, a pool, that is mining Dodge Coin. I tried to find something in the code for p2pool, but I
don’t know python and the code is too complex for my knowledge. -
So far i have not found an easy way to query that remotely…
-
I have added two url in the p2pool-feathercoin and send a pull request to https://github.com/andreasfaerber/p2pool-feathercoin/
if that will be included (by you??? ;) ) the url “/symbol” will return “FTC” and this could be used to determine the coin a pool is mining on.
the other one is /prefix" and returns the prefix defined in the networks.py of p2pool code
This is no short term solution, but at least it is a possible solution ;)
