Maybe you don't get my point. I think 3000+ users double check same hash numbers. I do not pretend I'm correct or that I understand. I just remember an old post of ByblePay saying multiple users "solved" same blocks in the pool.
Whatever is that botnet I think they use unique hash check code - it's open source. By my assumptions 100-200k unique hashes can beat our pool with 1 850 000 total hps. Anyway I continue to hoDL that machine in background HT cores with about 3100 hps. At some moment I'll hit 7000+ coins. Positive expectancy is because I'll not have fees and competitors aren't doing unique hash checks. If this is so then the most effective miner is solo machine. If I put 10 solo, then I'll increase the income by let's say 7 times not 10 (related to double hash checks between nodes).
Thanks! Thats what I want to talk about- I didnt want people to get the impression you did technical testing and proved the pool was worthless.
So about 20 days ago, I did an actual SQL test, because I save all solutions in the database for a period of time (every hash solution, every nonce, every exec biblehash constuent, so I can replay the solution if I want), and I did find about 15% of the solutions were being repeated.
To fix that, I added the 14 pool addresses, and started enforcing distinct nonce solutions. So now 100% of the solutions are distinct.
So no- no one is being awarded for the same solution anymore as anyone else. If miner X solves share Z with nonce 150, no one else in that round is allowed to solve a share with nonce 150 (work is rejected and then they receive a new share).
