There is a *new* and *different* bug that is impacting cgminer v3.4.2a+ and NiceHash ... I'm experiencing it on numerous boxes, and am trying to find a fix.  This is *NOT* the "idle bug" or it is not completely fixed in cgminer.

I'm mining SHA and when running using the "price" option in the password - p=0.07 - and letting it run for long periods of time, suddenly the NiceHash pool will appear in the miner as "Alive" ... but the pool is not passing any work, and the threshold has NOT been hit!  There are NO contracts for 0.07 ...

This is now easily reproducible on more than one box, and they are running the latest cgminer that does contain the "idle bug" fix.

I am trying now to debug the protocol, and determine exactly *WHY* cgminer would believe - when sending the miner.subscribe and miner.authorize requests - believe that the pool is alive.

When this happens my miners are sitting idle - believing they are connected to an active pool, but not being given any work.  Today I have lost hours of mining when I have come back to check the status of my miners and found them in this state.

I have reached out to NiceHash, ckolivas and kano for assistance, but any other assistance in debugging the protocol or cgminer would be appreciated.  Until I can know exactly how NiceHash is handling the protocol requests, it is very difficult to debug cgminer to see what is going on.