Hmm, a bit bigger issue here. Not sure if it used to do this or not, but it seems like the pool is getting, "stuck", on profitability estimates for extended periods of time, which causes it to report numbers that can be
very inaccurate.
Here's a screenshot of the x15 pool reporting rather old and inaccurate numbers for KoboCoin (sorry it's so large
). The pool at this point was reporting the difficulty of KoboCoin a whole 26 blocks--a good 8 minutes--behind the last block mined by the pool. In those 26 blocks, the mining difficulty had risen to nearly 3x what the pool was estimating--you can see how this would make the profitability estimate more than a little inaccurate.
Though I hadn't been paying it particularly close attention in the past, I get the impression that the pool didn't used to take this long to re-target; could some recent change perhaps be messing with the profit estimates?
It might also be worth noting that at one point during this stretch the difficulty in the top-left box corrected to report it at ~29 diff, but the profit estimate didn't change, and soon after (within a minute) it went back down to the incorrect 13.534 diff. Makes me think even more that something must be acting up. Variances between estimated and actual 24 hour profitabilities also seem unusually high for the algos with, "spiky", profitabilities (X15, X13, Quark, etc...).
EDIT: Just caught it being goofy with the estimates even after getting the proper difficulty.
Looks like the profitability estimates on the coins updated properly, but the change wasn't applied to the
current estimate for the algorithm, which seems to be stuck at what it was for the lower difficulty of KoboCoin (as is the rental price). Everything unstuck itself after maybe a couple minutes, but I'd imagine that the
current estimate isn't supposed to end up getting desynchronised with the coin stats for any length of time (I could be wrong, of course).