Another example of a fastblock being eaten by the same person in a couple seconds...
Am I the only one that thinks this is weird?
if you have "enough" volume, this is not unusual;
This guy has at least 3x of my plotted volume and likewise 3x as many fast combos.
A quick look into my miner log with deadlines <240 and distance to the preceding "fast" deadline;
block 69876 dl 15 distance 32
block 69878 dl 31 distance 2
block 70402 dl 93 distance 52
block 70407 dl 37 distance 5
block 70714 dl 203 distance 150
block 70720 dl 57 distance 6
block 70949 dl 110 distance 229
block 70950 dl 6 distance 1
block 70971 dl 214 distance 21
block 72096 dl 15 distance 19
block 72101 dl 199 distance 5
block 72103 dl 174 distance 2
block 72106 dl 110 distance 3
block 73335 dl 30 distance 77
block 73337 dl 7 distance 2
block 73805 dl 80 distance 64
block 73818 dl 20 distance 13
block 73819 dl 20 distance 1
block 74350 dl 37 distance 66
block 74352 dl 190 distance 2
block 74353 dl 213 distance 1
block 75723 dl 84 distance 22
block 75724 dl 121 distance 1
block 75887 dl 3 distance 68
block 75892 dl 18 distance 5
block 76198 dl 8 distance 15
block 76203 dl 36 distance 5
block 77490 dl 199 distance 11
block 77491 dl 199 distance 1
block 77493 dl 224 distance 2
block 78508 dl 41 distance 23
block 78509 dl 205 distance 1
and Blago, dude seriously your miner is crap, let alone the idiotic way it's coded you corrupt the heap all the time. You know in C, you gotta malloc(strlen(...)+1)
