Hmm, how is "jacobmayes94" related to this issue? As already said, there was a serious bug in ck's ckpool source code, which was unfortunately not discovered neither by ck's testing nor our testing (the bug was present in ck's solo pool as well as in our pool or any solo pool that was built on top of ckpool source code) - this bug was unfortunately hit by fredi. To explain what happened (simplified explanation): ckpool code was unable to handle generating found block to a multi-sig address (3xxx). When fredi was mining it was using multi-sig address and he was the first ever to find block when using mulit-sig address. When the block was found the ckpool code generated this block to a "random" Bitcoin address (ckpool converted the bitcoin address to hash160, and "inserted" that hash to coinbase tx).
That said: nobody (or actually someone random) has these 25 Bitcoins, therefore neither us nor ck- as the author of ckpool source code can't refund this. It's an unlucky event, but our solo pool service is free to use (only charge fee at block found event, the same as ck's solo pool) and we unfortunately can't guarantee for these kind of unlucky events. But as said, we addressed this issue immediately by refunding 100% of the costs that fredi had with renting hashing power (this refund came directly out of our pockets, since these 3+ Bitcoins were already paid to miners selling hashing power) to mine on solo pool and we also immediately worked with ck to solve this bug.
Best regards,
NiceHash