Quote from: kano on April 10, 2018, 10:05:28 AM

Quote from: roronoazoro2806 on April 10, 2018, 10:02:01 AM

Quote from: jhoren on April 10, 2018, 09:55:02 AM

Quote from: comby on April 10, 2018, 09:53:06 AM

The last reward block is actually missing?

It hasn't been paid out yet. We're only at 78 confirmations and I believe it doesn't pay out until 101.

Even still, from what I've read, the transaction is placed with low fees so it is only guaranteed to be paid out when we hit our next block after the 101 confirmations, but another block could pick them up.

Yes, reward will be sent after 101 confirms, but it can show up in reward page before that.
At the moment, I do not see the reward for the last block we mined.

On the previous page:
https://bitcointalk.org/index.php?topic=789369.msg34339237#msg34339237

As an aside for anyone wondering about pool issues, it's best to click on my name "kano" above my penguin icon, then click on "Show the last posts of this person." below "Additional Information:"

That will show you the last posts I've made which will of course include pool status information.

In turns out Daisy was wrong Sad

I'm transferring the correct "a2sr6 daisy" shift information over for a KDB restart soon.

And related to that:
There will be a KDB restart in a few minutes
This is the correction to the "a2sr6 daisy" shift.
This also, of course, includes a correction to the Block 517439 statistics since the shift had too many shares recorded in it.
The shares were duplicates, not shares lost from other shifts, so I only need to correct the one shift.

No mining will be affected by the KDB restart.
The web page will just show lotsa zeros and ?s until it completes - as per a normal KDB restart.

Although I've not yet found the bug in the code that causes it, I do know how it happens and when to expect the shifts to need correcting.
During a KDB reboot, the sequence processing code (that hasn't changed in a very long time) reported a large number of duplicate shares but didn't handle them correctly,.
This can only happen during a KDB restart, so it's not a problem that will appear without me knowing about it.

Restart shortly ...