I was looking at my worker shift information and noticed that in a few shifts the, Inv Diff had a 0. Should I be concerned?
How'd you get it to 0? i'm at .118% invalid and .170% block with 180th/s. I'd love me some 0 invalids!
Once Invalid Shares leaves zero, it can never come back to zero
for that block. You may still, however, have zero invalid-share
shifts within a block.
When we solve a block and start on the next one, Invalids resets to zero (no shares submitted, yet). Ideally, you want to keep it there.
Noobs like me ask, "Why?" Especially since Invalid shares don't affect your rewards. The short answer: efficiency. If your miner is submitting shares that it should "know" are out-of spec, it is wasting hashes. Almost every machine will produce Invalid shares at start-up; your miner only "knows" what's in its configuration. Once it handshakes and joins the pool to get feedback, things go "normal".
To keep Invalids as close to zero as possible requires that you adjust your miner's settings (pool node you're pointed at, frequency, voltage, etc). Your miner's status page (general info), and Kano Pool's Shifts page (~50 minute reference window for time) and Workers>Workers (check Show Details For Invalids) (specific types of Invalids (is the issue network or miner config?)) are helpful here.
For folks running new, out-of-the-box, state-of-the-art gear, this isn't too bad. When you have a garden of mostly someone else's problem children or older machines, like I do, it gets fun.
Also, a big
SHOUT OUT to Interinfinty for making that last block come in under 200%!!
MINE ON!!!
