So... it appears that the authors of this document either didn't grasp that open source software is not a purely cryptocurrency thing, or expected it to be obvious that this stuff only relates to implementations of cryptocurrency software. In which case... it's still broken, since essentially all such software depends on generic layers: are the glibc maintainers going to be bound by this stuff? What about LLVM and GCC? What about the Linux kernel? Compromise that, you've compromised the cryptocurrency wallet stuff...
(Never mind the obvious stupidity of trying to apply 'know your customer' regulations to something where the software is given away to anyone, so of necessity it would require both a time machine and telepathy to know even the simplest details about all future customers, let alone anything more -- not that open source developers can prevent some "customer" deemed unsuitable under the regulations from using the software anyway, since copyright licenses cover only distribution, not use, and if something is employed which does restrict use the software isn't open source any more.)
What on earth were they thinking?!
Biting the hand that feeds IT
