1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
|
Return-Path: <pete@petertodd.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id B6FE5955
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 21 Jun 2016 23:02:40 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from outmail148093.authsmtp.net (outmail148093.authsmtp.net
[62.13.148.93])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id ECDE715D
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 21 Jun 2016 23:02:39 +0000 (UTC)
Received: from mail-c247.authsmtp.com (mail-c247.authsmtp.com [62.13.128.247])
by punt20.authsmtp.com (8.14.2/8.14.2/) with ESMTP id u5LN2cAF008866;
Wed, 22 Jun 2016 00:02:38 +0100 (BST)
Received: from petertodd.org (ec2-52-5-185-120.compute-1.amazonaws.com
[52.5.185.120]) (authenticated bits=0)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id u5LN2Ys5060528
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Wed, 22 Jun 2016 00:02:35 +0100 (BST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
by petertodd.org (Postfix) with ESMTPSA id 417AB4010C;
Tue, 21 Jun 2016 23:00:32 +0000 (UTC)
Received: by localhost (Postfix, from userid 1000)
id A083020217; Tue, 21 Jun 2016 19:02:33 -0400 (EDT)
Date: Tue, 21 Jun 2016 19:02:33 -0400
From: Peter Todd <pete@petertodd.org>
To: James MacWhyte <macwhyte@gmail.com>
Message-ID: <20160621230233.GA10705@fedora-21-dvm>
References: <CAJowKg+zYtUnHv+ea--srehVa5K46sjpWbHVcVGRY5x0w5XRTQ@mail.gmail.com>
<20160621221347.GC10196@fedora-21-dvm>
<CAH+Axy59VfuiY7jp7CVrg0umt_AZydvYV8TP_RPUtEyGME9aCw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="ReaqsoxgOBHFXBhH"
Content-Disposition: inline
In-Reply-To: <CAH+Axy59VfuiY7jp7CVrg0umt_AZydvYV8TP_RPUtEyGME9aCw@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Server-Quench: 3e729854-3804-11e6-bcde-0015176ca198
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aQdMdAAUEkAaAgsB AmAbW1ReUF97WmU7 bghPaBtcak9QXgdq
T0pMXVMcUQAUfx5o RRseVBl3dQ0IcHZ4 ZghhC3dZVUx/cVt+
Sk5QCGwHMGF9OjNL BV1YdwJRcQRMLU5E Y1gxNiYHcQ5VPz4z
GA41ejw8IwAXBTpY REkIKkgfCV4RGSY7 XB0OVR8OJQUIVzk+
KQcnLVgHVFoWem8T CRN5AQ1AWwA8
X-Authentic-SMTP: 61633532353630.1038:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 52.5.185.120/25
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW
autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Even more proposed BIP extensions to BIP 0070
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2016 23:02:40 -0000
--ReaqsoxgOBHFXBhH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Jun 21, 2016 at 10:50:36PM +0000, James MacWhyte wrote:
> > 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-ce=
rtificate-blockchain/
> >
> > This is an extremely undesirable feature to be baking into standards gi=
ven
> > 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 wor=
ld
> identity, will be very useful to newly-developing use cases.
It's easy to confirm who is sending you money: give out different addresses=
to
different people, and keep those addresses private.
--=20
https://petertodd.org 'peter'[:-1]@petertodd.org
--ReaqsoxgOBHFXBhH
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
iQEcBAEBCAAGBQJXaceGAAoJEGOZARBE6K+yRgMH/RdK7sIx1D1nndOglebTeFmq
RqeX8OEcvE8hDGsaJQ6P0L+t3uptvU8Oc4y1XKKiyqHf3OOXJonxy2bqXoTUA2gR
jt1HX8ls/dk1pW1DRWpw0qwBqFrUsSvcyxutKCUEseoAeQsjgWvgvc4q8d9hNqxj
vxe0xojpCdMKkUSL3+VlsJS8xYJcdfEauUqZbkufvnetDf+onBdzaGB6WI6940hL
RB6VRom+Xf+Uee3turgWVCFnxEZrg9s6/rKvchdvyTS0XgEGQOUsK5bJb/vuja6t
h496ZOT6nUTV2nTE+5iiqVTScfbev657CzMlSojWe9qsVlPgVwmi6UKYgStNTAQ=
=90bJ
-----END PGP SIGNATURE-----
--ReaqsoxgOBHFXBhH--
|
