Re: [145+PH] KanoPool kano.is 7 BTC giveaway 🐈 US,UK,JP,NYA,DE,SG
...
Persoanlly, I think there is an issue in some detail yet to be discovered, that after the pool runs for an extended period of time, or so many shares, blocks are not found as near 100% as they should. ( when you use "probability" alone )
Persoanlly, I think there is an issue in some detail yet to be discovered, that after the pool runs for an extended period of time, or so many shares, blocks are not found as near 100% as they should. ( when you use "probability" alone )
Interesting theory...what changes during a mass reboot? vardiff readjusting for all workers is the one thing I think of, what else?
Shares (and blocks) are found by miners, not by the pool.
All shares that arrive are first checked/hashed by ckpool, then checked/hashed, from scratch, more accurately by KDB.
That's the only thing that shows if we find a block.
Any share that arrives, and hashes to a value that would produce a block, is displayed by KDB on the web site, no matter what other issues may occur.
(late, orphan, etc etc)
Any suggestion about random events causing blocks is actually caused by faulty memory
It's called 'Confirmation Bias' https://en.wikipedia.org/wiki/Confirmation_bias or in the more severe cases Cognitive Bias https://en.wikipedia.org/wiki/Cognitive_bias
It's typical to remember outstanding events and not notice the rest.