<div dir="ltr"><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Note that "client supplied identification" is being pushed for AML/KYC<br>
compliance, e.g. Netki's AML/KYC compliance product:<br>
<br>
<a href="http://www.coindesk.com/blockchain-identity-company-netki-launch-ssl-certificate-blockchain/" rel="noreferrer" target="_blank">http://www.coindesk.com/blockchain-identity-company-netki-launch-ssl-certificate-blockchain/</a><br>
<br>
This is an extremely undesirable feature to be baking into standards given it's<br>
negative impact on fungibility and privacy; we should not be adopting standards<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'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.</div></div></div>