Are you sure you're looking at the right coin? I don't see Bitconnect listed in the live coins.

This issue has been resolved. It turns out that when you declare a variable inside the scope of a "for" loop in Python, the variable still holds its value even after the loop is finished. In any other language, attempting to access the variable after the loop was finished would result in ...

The mining server isn't down, but live data is. I'm not sure that this post is related to the present issue.

Shouldn't that list be predicated on the cause of the crash?

Thanks for the fix Steve. I believe this is also impacting the profitability displayed by the pool for equihash.

Currently 0.00693691 BTC is being displayed as the profit, which if divided by 256 shows the true amount.

It was definitely a problem earlier, but appears to be working correctly now.

Steve, here are a couple of examples of what I was talking about. "version_bits must be null because this session did not request a version-rolling.mask. Provided version_bits: 20000000" "version_bits must be null because this session did not request a version-rolling.mask. Provided v...

Yes I didn't mean to imply that there was a problem with the shares being processed eventually, only that the processing was backing up because not all the recorders were running.

BTW it appears to be occurring again (EDIT: Looks like they've come back up as I posted this).

It was a 2 followed by however many 0s would be appropriate in that message. If I see that message again, I'll update with the full rejection message as I moved the S9 off this pool since it wasn't getting any hashrate accepted.

Actually I'd like to correct my previous statement. Some S9 are still having all of their hashrate rejected because of "version_bits must be null because this session did not request a version-rolling.mask". If it means anything it appears to always be a multiple of 10 shares which are bei...