<oembed><type>rich</type><version>1.0</version><author_name>npub18gjvug29c4yg46lmplq38e75gg6wn5mn8taytckcsr4jt8p74h3s5knkzl</author_name><author_url>https://nostr.ae/npub18gjvug29c4yg46lmplq38e75gg6wn5mn8taytckcsr4jt8p74h3s5knkzl</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2016-06-23&#xA;📝 Original message:On Thu, Jun 23, 2016 at 3:56 AM, Peter Todd via bitcoin-dev &lt;&#xA;bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&#xA;&gt;&#xA;&gt; In any case, I&#39;d strongly argue that we remove BIP75 from the bips&#xA;&gt; repository,&#xA;&gt; and boycott wallets that implement it. It&#39;s bad strategy for Bitcoin&#xA;&gt; developers&#xA;&gt; to willingly participate in AML/KYC, just the same way as it&#39;s bad for Tor&#xA;&gt; to&#xA;&gt; add wiretapping functionality, and W3C to support DRM tech. The minor&#xA;&gt; tactical&#xA;&gt; wins you&#39;ll get our of this aren&#39;t worth it.&#xA;&gt;&#xA;&gt;&#xA;Peter, BIP75 gives the parties transacting complete control over who they&#xA;choose to share their identity information with. This was the entire point&#xA;of the proposal. You authorize who you choose to give your payment address&#xA;to, and the sender can verify who they are sending payment to. All&#xA;communication and payment info are encrypted against third party snooping,&#xA;while still allowing asynchronous communication to accommodate ephemeral&#xA;mobile connections.&#xA;&#xA;The fact that some people will choose to use this identity information for&#xA;AML/KYC purposes doesn&#39;t detract at all from the fact that it gives bitcoin&#xA;users the tools they need to keep their payment information private, and&#xA;only communicate it with the parties they choose.&#xA;&#xA;Aaron Voisine&#xA;co-founder and CEO&#xA;breadwallet &lt;http://breadwallet.com/&gt;&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160623/a4f599d1/attachment.html&gt;</html></oembed>