Heh I did actually have some code to solve this - so I fired up the command and it's now fixed.
71.65% - another sub 100%
https://bitbucket.org/ckolivas/ckpool/src/43dc33a54caefc130570d403d8f95e89efa88c04/src/ckdb_cmd.c?at=master#cl-1003
Ever better 71.65% - another sub 100%
https://bitbucket.org/ckolivas/ckpool/src/43dc33a54caefc130570d403d8f95e89efa88c04/src/ckdb_cmd.c?at=master#cl-1003
it was actually 36.83%In case anyone was curious, the confirm set the block to the current in code numbers, but then a later check, resets them to the correct numbers based on the blocks range.
So this will also affect the next block (unless I restart ckdb before that)
It will show up as about 35% below what it really is on the web page and the first confirm stage.
But it will correct it about 20 seconds later with the correct values.
So until we get the next block, that number at the top will be about 35% below what it really is.
Either way 3 quick blocks are nice.
I did some fast math. pool has about 4000th right now
pull out the top 4 as they are too high pool drops from 4000th to 568 th
pull out ck and kano pool drops to 558 th pull out the bottom under 800gh
and the remaining qualified to win people have about 550th running so if you are running 2 sp20's at 2.5 th you have 2.5/550 chance to win. or about 220 to one.
if you are running 1 sp20 at 1.4th you have around a 400 to 1 chance to win.
.
)
