summaryrefslogtreecommitdiff
path: root/f6/8359d7075e759846b609551aa710c21d596ee9
blob: ced4adf8614176d283eded7cf10e80d30e956957 (plain)
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
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
Return-Path: <voisine@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id EFBB09C
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 23 Jun 2016 16:59:00 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-yw0-f178.google.com (mail-yw0-f178.google.com
	[209.85.161.178])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 4B9C0216
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 23 Jun 2016 16:59:00 +0000 (UTC)
Received: by mail-yw0-f178.google.com with SMTP id i12so75149459ywa.1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 23 Jun 2016 09:59:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc; bh=2Y265/Jr5rP06KOD3C42gP/CFsCnduYXJTkw/Vg2Adk=;
	b=ZsvUwJ2Fpk9SetT87U7d1K44N4a22jmjNvuwfUm6GLu1uiuXgJPRt5kgJs/UxNHWqr
	fhgppuH5WXBkDp00nJruoYOiMIcohnkNoNmW1roxtnvxKCSn7Qshvm6aZ7yj6df4aVOj
	bRMUkn8jiIXWjal+6ZVhEtK2SsMlw/Xa+/JdAQPmNtB77AfGUxPXGIs8dl1KwNp5GCfZ
	UiLyVOYEUCNgsQnlQHm6xvk6Hs0XIj6/hs/p2AH6Ph+jWnEp+as2VwCw1IkxHBT0IZHT
	qvpgIotxbx2k9FAIMiTAMx3VDjPwFqZ0BEH5Q4V3+ez+OqjSPsqS56EOQRBbDob6veqo
	TXKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc;
	bh=2Y265/Jr5rP06KOD3C42gP/CFsCnduYXJTkw/Vg2Adk=;
	b=c3MlqejBRrEcbmlLkZoO9BpXwbQuS/806mISpscrdxyOoBpMfWaU5fKqi8d1m/zeqr
	FDNoDS5cCU53+JF8ni/iequBAHMr+pv37GGfMUSrYbyAtrBpsYhFaLw26ygD1nBM8iMY
	j2b2f2Tz5dC8MP88CJDMGUxbw7PaAzHA4QIe2E04eusZ94uYfVoEvSnimQ17yX/LE/tb
	38Pn0RBOw2eSF4BXvAXqhOOhyQuJpcT2q6yEMZE7pGm1EcqTjFM95rX5dOZf7ScZiPw8
	/nMDFC1uERCZXMVftpgGWynS85lTeFshb2wbv5wWWwnTlxjVciLd/uNeChYQFVSpiQvM
	uqeA==
X-Gm-Message-State: ALyK8tJ1OoDF3j/5CFDGkojecFkppel+udiPZYCFLhNmKv+N1N1c4W/7PivdEBK2VY3N0DL9YPXDnZAGVuD4NA==
X-Received: by 10.37.116.135 with SMTP id p129mr20205114ybc.101.1466701139478; 
	Thu, 23 Jun 2016 09:58:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.13.243.133 with HTTP; Thu, 23 Jun 2016 09:58:58 -0700 (PDT)
In-Reply-To: <20160623105632.GB19241@fedora-21-dvm>
References: <CAJowKg+zYtUnHv+ea--srehVa5K46sjpWbHVcVGRY5x0w5XRTQ@mail.gmail.com>
	<20160621221347.GC10196@fedora-21-dvm>
	<CABqynxJCiXL0djx+xt9i=HJqC=0=5sZ9ecL7k1_a_XHiJ8qibw@mail.gmail.com>
	<20160623105632.GB19241@fedora-21-dvm>
From: Aaron Voisine <voisine@gmail.com>
Date: Thu, 23 Jun 2016 09:58:58 -0700
Message-ID: <CACq0ZD6-gjjahdrpqk4UVHn+oOZw3dgFnV5opKLSimwpw7Mxtg@mail.gmail.com>
To: Peter Todd <pete@petertodd.org>, 
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a114dd2c6690ea90535f4f845
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
	RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.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: Thu, 23 Jun 2016 16:59:01 -0000

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

On Thu, Jun 23, 2016 at 3:56 AM, Peter Todd via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

>
> In any case, I'd strongly argue that we remove BIP75 from the bips
> repository,
> and boycott wallets that implement it. It's bad strategy for Bitcoin
> developers
> to willingly participate in AML/KYC, just the same way as it's bad for Tor
> to
> add wiretapping functionality, and W3C to support DRM tech. The minor
> tactical
> wins you'll get our of this aren't worth it.
>
>
Peter, BIP75 gives the parties transacting complete control over who they
choose to share their identity information with. This was the entire point
of the proposal. You authorize who you choose to give your payment address
to, and the sender can verify who they are sending payment to. All
communication and payment info are encrypted against third party snooping,
while still allowing asynchronous communication to accommodate ephemeral
mobile connections.

The fact that some people will choose to use this identity information for
AML/KYC purposes doesn't detract at all from the fact that it gives bitcoin
users the tools they need to keep their payment information private, and
only communicate it with the parties they choose.

Aaron Voisine
co-founder and CEO
breadwallet <http://breadwallet.com/>

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

<div dir=3D"ltr">On Thu, Jun 23, 2016 at 3:56 AM, Peter Todd via bitcoin-de=
v <span dir=3D"ltr">&lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation=
.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>&gt;</span=
> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-widt=
h:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-le=
ft:1ex"><div><div class=3D"h5"><br></div></div>
In any case, I&#39;d strongly argue that we remove BIP75 from the bips repo=
sitory,<br>
and boycott wallets that implement it. It&#39;s bad strategy for Bitcoin de=
velopers<br>
to willingly participate in AML/KYC, just the same way as it&#39;s bad for =
Tor to<br>
add wiretapping functionality, and W3C to support DRM tech. The minor tacti=
cal<br>
wins you&#39;ll get our of this aren&#39;t worth it.<br>
<div class=3D""><div class=3D"h5"><br></div></div></blockquote><div><br></d=
iv><div>Peter, BIP75 gives the parties transacting complete control over wh=
o they choose to share their identity information with. This was the entire=
 point of the proposal. You authorize who you choose to give your payment a=
ddress to, and the sender can verify who they are sending payment to. All c=
ommunication and payment info are encrypted against third party snooping, w=
hile still allowing asynchronous communication to accommodate ephemeral mob=
ile connections.</div><div><br></div><div>The fact that some people will ch=
oose to use this identity information for AML/KYC purposes doesn&#39;t detr=
act at all from the fact that it gives bitcoin users the tools they need to=
 keep their payment information private, and only communicate it with the p=
arties they choose.</div><div><br></div><div><div>Aaron Voisine</div><div>c=
o-founder and CEO<br><a href=3D"http://breadwallet.com/" target=3D"_blank">=
breadwallet</a></div></div><div>=C2=A0</div></div></div></div>

--001a114dd2c6690ea90535f4f845--