Our first 'almost' block - but it wasn't good enough.
ckpool submits the share as a block if it is within a small amount of being a block just to be sure.
So it shows up on the web site, but alas not good enough.
share block was: 52123573961.901596
but current diff is: 52278304845.59168243
It will show up as an orphan, but I guess I need to label it as something else later since it's not an orphan.
I think there are bigger issues, I see the Pool is on the SAME Block as the NETWORK now!!!
Not sure what you mean there?
All workinfos that ckpool works on are from calling bitcoind getblocktemplate
(yeah GBT is pretty poorly written in bitcoind but we call it since it is the reference standard code)
At the time when our "368348 block" was found we were working on confirming block height 368347.
Since our bitcoind rejected our "368348 block", we continued to build on block height 368347 that was before ckpool submitted the rejected block - since there was no new block known anywhere.
When some other pool found 368348, we then switched to building on their new 368348 block as expected.
We don't do SPV mining and we don't build empty blocks as an excuse for having crap slow pool code.
We don't need to, our block change handling is probably one of the fastest of all pools on the network.
At no point during that time when ckpool submitted our rejected "368348 block" did any miner on the pool begin work on building on our rejected "368348 block"