Prohashing Mining Pool Forums

Yesterday, I discovered and Vance resolved a bug that negatively affected ethash profitability. The expected payouts of some coins were lowered by as much as 30% because blocks were incorrectly marked as orphaned. The cause of the problem was that the wrong hash values were being used to search for blocks on the blockchain. When no block with the wrong hash value was found, the coin would be placed into error.

After the bug was resolved, I reviewed the most difficult ethash coins and manually corrected exiting blocks. That increased ethash profitability, and the changes are effective now.

There is still something a bit off with ethash algo. I have 2 rigs pointed at coin Ethereum Classic and it's been going into coin error a few times today. I am getting the following error:

ETH: Received error: {"id":14,"result":null,"error":[-2,"Staleshare",null]}

It seems to correct itself however since whatever change been made, this is occurring often. On the Live mining Failures side on prohashing, it'll show the coin/algo is in error as a message. So far today this has occurred 3 times. Might want to keep an eye out.

Thanks

mstrozier wrote: ↑Fri Feb 07, 2020 11:51 am There is still something a bit off with ethash algo. I have 2 rigs pointed at coin Ethereum Classic and it's been going into coin error a few times today. I am getting the following error:

ETH: Received error: {"id":14,"result":null,"error":[-2,"Staleshare",null]}

It seems to correct itself however since whatever change been made, this is occurring often. On the Live mining Failures side on prohashing, it'll show the coin/algo is in error as a message. So far today this has occurred 3 times. Might want to keep an eye out.

Thanks

Thanks for the heads up. I'll look into this first thing in the morning, although it sounds like it's going to be quite difficult to reproduce.

knock on wood, I haven't seen any further errors as the day progressed. Was only this morning. I'll keep an eye out on my logs if it happens again.