Quote from: Claymore on May 14, 2016, 09:06:13 AM

Quote from: Talan on May 14, 2016, 08:38:47 AM

Quote from: Claymore on May 10, 2016, 03:32:36 PM

Quote from: melloyellow on May 10, 2016, 03:12:19 PM

Claymore, is this fix relevant to your miner

https://github.com/Genoil/cpp-ethereum/issues/36

It could fix some low difficulty shares, at least in ethminer.

My miner does not use any sources from ethminer, so any bugs/fixes related to ethminer are not related to it.

Hi Claymore,
I'm also wondering how your miner handles such cases what genoil has fixed here: After having received a new job, will your miner still submit stale shares for the replaced job?

In fact, stale shares are invalid shares. If some pools want to get stale shares I will add such option, but some pools can count stale shares as invalid shares and you will ask me why miner sends more invalid shares. Therefore I will check all popular pools how they work with stale shares, so I can decide if this option must be enabled or disabled by default. Anyway, I will add this option in next update.
BTW, stale shares rate is less than 1% for my miner.

Hi Claymore,

Thanks for taking this up. How about you keep it simple by adding one commendline option to send stale shares and keep the status quo as default?
This way, there won't be a need to check all pools as anyways this could change over time. I heard that miningpoolhub and ethpool/ethermine accept stale shares as they could result in uncles.

Thanks