Rifts are sad events and they suck. Hard.

kano, it's understandable for ck to not use ckdb as he's mentioned that the db stuff is beyond his remit. As a result he has a dependency on you to test that commits don't introduce retroactive bugs in ckdb. You're really the best person for that as you run it in production and are the only person doing so openly. If you're using an old version of it (August 2016), the private fork happened then, not now.

Re: the private CDF calcs: I can digg that it very much classifies as secret-sauce for a pool. If a pool is a government, defense materiel would definitely include custom, unshared BWH-protection and/or luck-based pool operator actions. Warnings that lead to bans and eventual non-payment is serious shit and affects your reputation as a solid pool operator. So you have to protect that.

As someone who's been working on wrapping my head around the whole segwit thing (the tech, et al aspects of it) I can say that you have both been invaluable inputs on providing unfettered-, independently- and well-formed opinions on what will be a big change for bitcoin. Or not. Your polar opposite views on the whole thing is an example of what bitcoin is: people arguing until they're pissed at one another and eventually coming up with something that works for both of them. It's a good thing. This situation is not all that different.

Disagreements are important. In any venture: When two men always agree, one of them is unnecessary. The work you both do is as inter-dependent as it is important.

https://www.youtube.com/watch?v=JYc05gZFly0

W