We are all on the same team... no one is screaming at anyone... this needs to be fixed as soon as possible for many reasons... and the best way to find a fix is to work with experienced pool operators and community members with expertise. So happens that Criptoe Pools has 2 very experienced and knowledgeable coders, so we are doing everything we can to get KDC back on track again.

And I am sure that 'hash.so' has something to contribute that we may have missed... this is a team effort... and the fork are not going to go away on their own.