Has your miner been idling? I'm asking because we noticed (and fixed) an issue that caused some of the work packets to be potentially incompatible with some mining clients for the last ~3 days. It can only have impacted a very small amount of users because overall hashrate did not change.
Would this have anything to do with the 30% stales you were submitting to Ozcoin the other day?
Hi Graet, welcome in our thread!
The abovementioned issue is not related. It had to do with an upstream pool, but not Ozcoin
Let me elaborate on the Ozcoin incident:
Ozcoin has two servers (au and us). The stales you were noticing were occurring only on one of Ozcoins servers. We took that ozcoin server out of rotation for a day. Now it seems to be functioning OK again, so it's back in. You mentioned some backend problems around that time? We attributed it to that and did not pay further attention to it. Overall our experience with Ozcoin has been excellent.Now for all the ABC miners that might have become worried by a mention of 30% stales:ABC miners were in no way impacted by those ozcoin stales
. share accounting for ABC miners is completely seperated from what upstream pools like Ozcoin are reporting. If ABCPool determines a share to be valid the user gets credited, even if an upstream pool reports it as invalid.
Why is that? Well, the promise we make to our miners has nothing to do with the performance of third parties. Therefore we think it wouldn't be fair to ABC miners if we shifted problems with third parties to them. Our miners have a 'contract' with us, and we have further 'contracts' with third parties. Seperate.
That's also where ABCPool improves on services like Project #2 or GPUMAX. Their users are experiencing a fluctuating amount of stales, because they apply the upstream result to the user instead of doing their own verification. IMHO, such an approach can never provide miners with a predictable experience.