Confirm, nicehash cnr mining - many rejected shares - job not found.
And "Dev pool connection was closed by remote side. Mining will proceed at reduced rate etc etc"
Hey guys! Sorry about all the mess with dev pool, there are some issues outside of our control that we are addressing, should hopefully be resolved today. However, I do believe you all see a reconnect within 30 secs or so, so the "reduced rate" period should really be minimal. Let me know if you are experiencing longer disconnected periods than 30-60 secs.
What about high amount of rejects due to "job not found" on nicehash?
The one big difference is that open source miners have excellent cpu code for the algo, borrowed from their cpu miner. For rigs with slow celerons, we will add significant latency with our more naive on-cpu verification. We need to implement automatic generation of x86 machine code for the random ops in CN/r, quite annoying crap to spend time on, but we dont really have a choice it seems.
Fix for now: if your rig(s) are running without any hw errors, try running with no_cpu_check. This will disable our check and let the pool run the check instead. Will be fine on most pools and if you dont oc so much that you get invalid shares that you flood the pool with

.