from my perspective, CoinKite's CTO is the party with the highest likelihood of intentional malice, followed by other technical leadership at that company.
Nothing definitive but the obfuscation of the author of the vulnerable library that was introduced coupled with some choice CoinKite comms are pretty damning. And then there's the whole blockclock phone home.
quotinglooks like there was a USB vuln between 4.0.0 and 4.0.1 that would be referenced to. given USB as the threat vector, an air gapped setup would not be affected. I don't believe he is complicit based on a number of things but this needed some clarification
nevent1q…y8fv

