Just a quick update about the KDB code
I've already told everyone this in Discord, but in case anyone doesn't go there:
I updated KDB last night, this was for the addition to the txn/payments to identify the new Owed+Block payments separately for the standard Block payment.
You get one of these if you have an outstanding dust balance when you've also earned above dust in the current reward.
That's all running OK now and yesterday's block is also showing fully on the Payments page.
The Rewards page of course has always been up to date.
This update also included a couple other things people may (or may not) notice on the web site:
The block difficulty calculation is now correct ...
Alas once we fell into the realms of a small pool, taking multiple diff changes per block, using BlockWork/CurrentDiff is going to get more and more incorrect.
What you'll see now, when there is a Diff change, is the % will not suddenly jump up or down, but continue on from the value it was at the time just before the diff change.
Some time in the future I'll update the block stats of the past year or so, where this fix should make a noticeable difference for those blocks.
The change I made for this is to make the running diff total also do a running diff% total - i.e. add the diff% per each share as it arrives.
This does lead to an issue with the accuracy of the largest floating point number in C, so it can get out by a small amount after about 4-5 decimal places if there are a lot of low diff shares - which here the diff is limited to 442.
But as has always happened with KDB, the % shown is always recalculated after the block is confirmed, and that recalculation overcomes the accuracy issue.
In the (distant) future, as difficulty rises, this will become more of an issue with the running total diff%, but the recalculation itself will still be ok.
KDB also reports to me on the console, the floating point accuracy for the current difficulty, when KDB starts.
On your workers page, I've adjusted the calculation for "Invalid"
It no longer includes "Hi" or "Dup" in the "Invalid" calculation, since they have no expected effect on rewards.
They're caused by the firmware in your miner, not the pool.
"Dup" is of course when your miner sends the same share more than once.
"Hi" is when your miner is sending shares above
and below the difficulty specified - it counts the ones below.
Of course you can still see the "Hi" and "Dup" values, same as before.
The above change has also been applied to the pool "Invalids:" number at the top left of every page.
The solo changes are the next main update ... as yet unknown when, though a lot of those changes are already in the code now live, since I've tested that they're ok for just normal pplns before doing this update.
