{"type":"rich","version":"1.0","author_name":"npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2","author_url":"https://nostr.ae/npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2016-06-21\n📝 Original message:On Tue, Jun 21, 2016 at 10:50:36PM +0000, James MacWhyte wrote:\n\u003e \u003e Note that \"client supplied identification\" is being pushed for AML/KYC\n\u003e \u003e compliance, e.g. Netki's AML/KYC compliance product:\n\u003e \u003e\n\u003e \u003e\n\u003e \u003e http://www.coindesk.com/blockchain-identity-company-netki-launch-ssl-certificate-blockchain/\n\u003e \u003e\n\u003e \u003e This is an extremely undesirable feature to be baking into standards given\n\u003e \u003e it's\n\u003e \u003e negative impact on fungibility and privacy; we should not be adopting\n\u003e \u003e standards\n\u003e \u003e with AML/KYC support, for much the same reasons that the W3C should not be\n\u003e \u003e standardizing DRM.\n\u003e \u003e\n\u003e \u003e\n\u003e KYC isn't the only use case. There are other situations in which you would\n\u003e want to confirm who is sending you money. Making it *required* would of\n\u003e course be a horrible idea, but allowing people to identify themselves, in\n\u003e many cases with an online-only identity that isn't tied to their real world\n\u003e identity, will be very useful to newly-developing use cases.\n\nIt's easy to confirm who is sending you money: give out different addresses to\ndifferent people, and keep those addresses private.\n\n-- \nhttps://petertodd.org 'peter'[:-1]@petertodd.org\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 455 bytes\nDesc: Digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160621/0cbe3456/attachment.sig\u003e"}