On 6/23/2016 1:56 PM, Peter Todd via bitcoin-dev wrote: >> >> I don’t know if you are opposed to organizations that have AML requirements >> from using the bitcoin blockchain, but if you aren’t, why wouldn’t you >> prefer an open source, open standards based solution to exclusionary, >> proprietary ones? > > In some (most?) countries, it is illegal to offer telecoms services without > wiretap facilities. Does that mean Tor builds into its software "open source" > "open standards" wiretapping functionality? No. And interestingly, people > trying to add support for that stuff is actually a thing that keeps happening > in the Tor community... > > In any case, I'd strongly argue that we remove BIP75 from the bips repository, > and boycott wallets that implement it. It's bad strategy for Bitcoin developers > to willingly participate in AML/KYC, just the same way as it's bad for Tor to > add wiretapping functionality, and W3C to support DRM tech. The minor tactical > wins you'll get our of this aren't worth it. > Exactly! Totally agree with Peter Todd. There's absolutely no gain for Bitcoin to willingly participate in AML/KYC. Plus this might come with strings attached: for example when running a Tor relay in some countries if you interfere with the traffic (censor, limit, filter, etc.) you become responsible for it, while when you only relay anonymous traffic without interfering or having the possibility to do so (installing certain tools, using a modified Tor which allows you to do so, etc.) you cannot be held responsible for the traffic. Any kind of built-in AML/KYC tools in Bitcoin is bad, and might draw expectations from _all_ users from authorities. Companies or individuals who want and/or need AML/KYC can find ways and do it at their side isolated from the entire network, and the solutions shouldn't come from upstream. AML/KYC/ differ from country to country and will be hard to implement in a global consensus network even if it would be worth it.