MIME-Version: 1.0
References: <CAJowKg+zYtUnHv+ea--srehVa5K46sjpWbHVcVGRY5x0w5XRTQ@mail.gmail.com>
	<20160621221347.GC10196@fedora-21-dvm>
In-Reply-To: <20160621221347.GC10196@fedora-21-dvm>
From: James MacWhyte <macwhyte@gmail.com>
Date: Tue, 21 Jun 2016 22:50:36 +0000
Message-ID: <CAH+Axy59VfuiY7jp7CVrg0umt_AZydvYV8TP_RPUtEyGME9aCw@mail.gmail.com>
To: Peter Todd <pete@petertodd.org>, 
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
	Erik Aronesty <erik@q32.com>
Content-Type: multipart/alternative; boundary=001a114fca4ac5cdb60535d1a611
Subject: Re: [bitcoin-dev] Even more proposed BIP extensions to BIP 0070
Precedence: list

--001a114fca4ac5cdb60535d1a611
Content-Type: text/plain; charset=UTF-8

> Note that "client supplied identification" is being pushed for AML/KYC
> compliance, e.g. Netki's AML/KYC compliance product:
>
>
> http://www.coindesk.com/blockchain-identity-company-netki-launch-ssl-certificate-blockchain/
>
> This is an extremely undesirable feature to be baking into standards given
> it's
> negative impact on fungibility and privacy; we should not be adopting
> standards
> with AML/KYC support, for much the same reasons that the W3C should not be
> standardizing DRM.
>
>
KYC isn't the only use case. There are other situations in which you would
want to confirm who is sending you money. Making it *required* would of
course be a horrible idea, but allowing people to identify themselves, in
many cases with an online-only identity that isn't tied to their real world
identity, will be very useful to newly-developing use cases.

--001a114fca4ac5cdb60535d1a611
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_quote"><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">Note that &quot;client supplied identification&quot; is being pushed fo=
r AML/KYC<br>
compliance, e.g. Netki&#39;s AML/KYC compliance product:<br>
<br>
<a href=3D"http://www.coindesk.com/blockchain-identity-company-netki-launch=
-ssl-certificate-blockchain/" rel=3D"noreferrer" target=3D"_blank">http://w=
ww.coindesk.com/blockchain-identity-company-netki-launch-ssl-certificate-bl=
ockchain/</a><br>
<br>
This is an extremely undesirable feature to be baking into standards given =
it&#39;s<br>
negative impact on fungibility and privacy; we should not be adopting stand=
ards<br>
with AML/KYC support, for much the same reasons that the W3C should not be<=
br>
standardizing DRM.<br><br></blockquote><div><br>KYC isn&#39;t the only use =
case. There are other situations in which you would want to confirm who is =
sending you money. Making it *required* would of course be a horrible idea,=
 but allowing people to identify themselves, in many cases with an online-o=
nly identity that isn&#39;t tied to their real world identity, will be very=
 useful to newly-developing use cases.</div></div></div>

--001a114fca4ac5cdb60535d1a611--