Well in case anyone was wondering about pool changes (and someone commented before)
Blocks have been found since all changes that have occurred.
i.e. the pool does find blocks with the current configuration.
I'm not using any of the current ckpool git segwit which doesn't work.
The bad luck itself (as I posted before) has quite clearly been since the last block in November.
Now for some statistics (since the middle of May) I mentioned I'd post sooner or later:
Name CDF[Erl]
S9v1 0.994766 103.6 BDR 79 Blocks
strat 0.8.x 0.883100 15.0 BDR 11 Blocks
A6+? 0.881335 83.2 BDR 73 Blocks
proxy 1 0.776782 6.5 BDR 5 Blocks
A7v1 0.772224 6.5 BDR 5 Blocks
S7+S5+?(4.8) 0.627001 307.3 BDR 302 Blocks
ckpool 5.7 BDR 6 Blocks
S?+? (4.7) 0.298274 16.5 BDR 19 Blocks
S9v2 0.223353 10.2 BDR 13 Blocks
A?+? (4.9) 0.040362 143.3 BDR 165 Blocks
strat 0.5/0.6 0.4 BDR 0 Blocks
Total 668.1 BDR 678 Blocks
'strat' is stratehm stratum proxy
The total stats since May is:
Block finders: 753.8 BDR 750 Blocks
Non-block Finders: 3.5 BDR
I have always been after this type of data, or more to the point the raw data underneath. I am not sure what BDR is or what the math is behind your CDF figure but given the raw data is it possible for you to confirm that all of the devices are finding a similar number of blocks on average for the same amount of work. I want to put to bed the conspiracy that a particular type of miner firmware could send a low number of successful blocks to a different IP than the pool it is working for. A single UDP packet containing a small simply encrypted string to a common range of IP addresses such as one in AWS would be difficult to spot but 1 in a 100 or so additional found blocks would certainly help a pool out. Data like this would help to spot an underperforming type of miner.