Now, regardless of how it is done, the idea is to determine if a fork is worthy of being able to call itself a KMD fork. It must be a complete fork of KMD if it is advertising itself as that. And if it saying it has made improvements to KMD, then that also must be demonstrated. So we will post a report card on the status as we find out about these forks. It might not be updated in a realtime fashion as you have said we have more important things to do, and the burden is on the fork to prove themselves.

From what I have seen the changes made to fix the hashrate issues will be ineffective and does not address the real security issues that they have already been notified about. I guess it is more important to prevent any notary mined coins from being used than to actually fix the coin. Until SAFE is an actual KMD fork and safe from the known attack vectors, we reserve the right to field test the new versions against the claimed fixes. It just isnt responsible to release known vulnerable code. However any coins gained from such activities will be set aside for the future development of that fork and it wont be sold off on the open market.