CSZiggy wrote:I think the issue before was the profits were down 10% or more from other places. If all you did was fix a display error so it now shows the correct hashrate but didn't touch the profit then nothing has changed has it? Difficulty dropped last night on the litecoin network, so litecoinpool rose in its payouts and should stay that way for the next 3 days until the next difficulty readjustment.
Before I would hash on here at 550 instead of 600, and I got paid for 550 hash.
Now it shows I'm hashing at 600, but still only getting paid like I was hashing at before at 550.
If I'm now making MORE hash but at the same total rate as before since it was just a display error, does that mean the pool is paying even LESS now per MH? If I made $100 at 550 hash and now I'm making $100 at 600 hash, isnt the 1MH/s payment now even lower than it was before? So were the expected MH/s charts wrong as they have been using larger time intervals to determine expected payouts all this time? Or do the charts use the actual shares recorded and not the time bucket method to compute profits?
There has been no change in payouts. Whether the amount paid is correct or incorrect, the issue that was resolved was solely a display issue. It's explained in a different thread if you're interested in the details. Because the display issue for hashrate was resolved (which increased displayed hashrate), displayed profitability may decline, because profitability is total earned / hashrate. However, since litecoin difficulty declined at the same time, it's likely that today's displayed profitability will remain the same as yesterday's.
As to earnings, that's definitely a separate issue. I ran some queries into this problem and I found some interesting data - it turns out that we are somehow luckier than average across almost all coins, which is improbable. This issue was never noticed before because there were many other errors (like the weights issue and the low hashrate issue) that hid it. At the same time, we noticed that the getdifficulty() method of NewYorkcoin returns a different difficulty that mismatches the getblocktemplate()'s "bits." If we are using the wrong difficulty to submit blocks, that means some blocks are being accidentally withheld from the network and we can improve profits by fixing that.