Page 1 of 1
Poolpicker reporting incorrect payouts
Posted: Wed Mar 16, 2016 9:09 am
by Steve Sokolowski
Hi,
Poolpicker.eu is reporting incorrect payouts for our pool. Apparently, instead of parsing our data and using the provided data for each date, they take the most recent reported date and store that value in their database. Because other pools appear to be based in Europe and Asia, their statistics are shifted a day forward from ours as a result of Poolpicker's implementation. For example, we actually earned 5.00 cents yesterday, but they are reporting only 4.5.
Chris sent an E-Mail to Poolpicker requesting that they review their code and parse the dates correctly. He also asked them to explicitly specify whether the reported values are expected to be before or after fees, as it isn't clear which value the pools are reporting.
Regardless of what they do, our accurate earnings are always posted on the "charts" page, so you can get a better idea of what the pool is earning from there. We'll keep you updated about the outcome of this issue.
Re: Poolpicker reporting incorrect payouts
Posted: Sun Mar 20, 2016 9:03 am
by Steve Sokolowski
The owner of Poolpicker has continued to refuse to respond to our messages. There are two issues: they will not publicly state whether the values are computed before or after fees, and they are incorrectly parsing the dates.
If they choose not to reply this week, we will be requesting removal from Poolpicker, as they are not accurately reporting our earnings.
Re: Poolpicker reporting incorrect payouts
Posted: Sun Mar 20, 2016 4:28 pm
by Minerman
I know that Nicehash is reporting before the fees. Making it impossibloe to compare the pools. The only right way to report is after the fees.
Re: Poolpicker reporting incorrect payouts
Posted: Mon Mar 21, 2016 8:55 am
by Steve Sokolowski
Ah, so that's why they are reporting such high numbers.
Chris is going to call the owner, as he left his number in the signature line of a previous E-Mail. Thanks for the tip. Knowing that, we will discontinue our feed if they refuse to set guidelines on reporting.
Re: Poolpicker reporting incorrect payouts
Posted: Thu Mar 24, 2016 10:34 am
by Steve Sokolowski
Effective tomorrow, Chris will be changing the way earnings are reported to Poolpicker. None of the changes will affect what customers actually earn.
First, he's going to report one day ahead, because Poolpicker is delaying its earnings by a day. That means that our earnings will better match what others are reporting in terms of time. Second, he is going to increase what is reported by the pool fee, because others are stretching the truth and reporting what they pay before fees are deducted.
Poolpicker is still an unreliable source of data because they don't standardize which timezone the earnings should be reported for. These changes will allow us to report as best as possible, but we encourage people to mine with pools to determine their profitability, since Poolpicker's data collection is self-reported and the daily reporting periods are not consistent.
Re: Poolpicker reporting incorrect payouts
Posted: Mon Mar 28, 2016 5:00 pm
by Steve Sokolowski
Through referral logs, I was able to get to the bottom of this:
https://medium.com/@webbson/prohashing- ... .lzty9mk4j
By coincidence, the owner removed us at the same time we had made the decision to request removal. A few days ago, someone pointed out that we had disappeared and we simply decided not to complain - this apparently is why it had happened.
Re: Poolpicker reporting incorrect payouts
Posted: Fri Apr 08, 2016 10:47 am
by Minerman
Clevermining is better than prohash?
Clever : 0,000112
PRo: 0.000094
How come Prohash is not at the top with all the whissles?
Re: Poolpicker reporting incorrect payouts
Posted: Fri Apr 08, 2016 3:05 pm
by Chris Sokolowski
Other pools' profitability reporting is questionable since there is no standard for reporting, as Steve has stated in the past at
http://forums.prohashing.com/viewtopic.php?f=11&t=781. I suggest mining with a pool over a long period to determine its profitability.