No Connection

have machines been blocked can't connect any of my mats to the pool anymore

also, the total hash rate dropped from around 100 to 70ghs that's a lot of machines

It appears the pool is not working.

There was an issue with our router tonight that was causing some miners' connections to be rejected. I have fixed the problem. You shouldn't have any more issues, but I will be happy to help if you still need assistance.

Thanks working again

Will the API for total Hash rate ever be fixed?

bachel wrote:Thanks working again

Will the API for total Hash rate ever be fixed?

I'm a little confused about the issue. Are you saying that you just want the total hashrate of all of your workers to be provided in the API? If so, couldn't that be easily calculated by simply iterating through them all and adding the numbers?

Or, were you referring to the total hashrate of the pool?

yeah could b easily done actually but that's what your API returns so it has the total already but is displaying null and things like that really really bugs me

{
"acceptedHashrate": null,
"rejectedHashrate": null,
"workers": [
{

One other thing I think the fault is on my site but I can't get any data from your public https://prohashing.com/exchange/instantProfitability from another webserver browser yes through PHP or angular no I always get the not allowed answer I am building a calculator site and would like to include your pool

bachel wrote:yeah could b easily done actually but that's what your API returns so it has the total already but is displaying null and things like that really really bugs me

{
"acceptedHashrate": null,
"rejectedHashrate": null,
"workers": [
{

One other thing I think the fault is on my site but I can't get any data from your public https://prohashing.com/exchange/instantProfitability from another webserver browser yes through PHP or angular no I always get the not allowed answer I am building a calculator site and would like to include your pool

I'll look into these issues and get back to you within a few days. Hopefully, they are simple things to fix.

I'd also like to get the WAMP interface out there instead of REST, so that people can display live data rather than using polling. That might be worth devoting time to while Chris is engaged in X11 testing.

That would be great thanks

bachel wrote:That would be great thanks

OK, I looked into this problem.

It turns out that this is a bug. The issue has been present for a while, but I guess people just added the worker hashrates together and didn't report it.

I fixed this bug in the "multiple algorithms" system, which is going to enter public testing in 10 days. We expect to completely eliminate the "single algorithms" system within two months, so all non-essential development on it has stopped. It would take three hours to fix this in the single algorithms system, and that work would be wasted, so hopefully you can understand my desire to just wait for the new system to carry through the fix.

Your report brought up an interesting issue that I want to address after we release multiple algorithms: whether certain features are used often enough to justify continued maintenance. In this case, once we get real-time WAMP updates working, would you even use the REST endpoint anymore? The REST data is delayed between 90-180 seconds, while the WAMP data is delivered every 50ms and uses less bandwidth.

I was thinking we should just announce the deprecation of this REST API, once WAMP is out and you have a chance to convert, so that we only have to maintain one API (the better one). Your thoughts?

100% with you on that as long as you can handle the requests for the live data

I really like what you guys are doing here