summaryrefslogtreecommitdiff
path: root/16/260d7e73f7ae2ea59428e955735da00498821d
blob: d101991eb113f064e0d6acdff178e9432765a38f (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
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <paul@airbitz.co>) id 1YJUaQ-0001mp-LE
	for bitcoin-development@lists.sourceforge.net;
	Thu, 05 Feb 2015 22:07:46 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of airbitz.co
	designates 74.125.82.171 as permitted sender)
	client-ip=74.125.82.171; envelope-from=paul@airbitz.co;
	helo=mail-we0-f171.google.com; 
Received: from mail-we0-f171.google.com ([74.125.82.171])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1YJUaP-0008TX-5h
	for bitcoin-development@lists.sourceforge.net;
	Thu, 05 Feb 2015 22:07:46 +0000
Received: by mail-we0-f171.google.com with SMTP id k11so10274246wes.2
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 05 Feb 2015 14:07:39 -0800 (PST)
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:content-type;
	bh=Ox6wh3R6YoUARtHFy4jT3/gxkRWSasYcXFuvCDc6R8g=;
	b=fdwvAA5WtUNC7dSZJBxNCNncBynWO77DArRTqsSATh4IIKWg0h5DyA6TN3LQlXXMAx
	s0UNJIfPghdOjOAccx/1J34GebzVHWwxcN4DPJP/BNTXmb6fRC+DduylBkHc5EFYWlEP
	SuWjCITxtXOIRf9PrgaKdYjTt7F+SY1w6xsGJZ22oLsaStxgROWPicihEtTj83t1MtqR
	/hhEkkaRBPVYqCIBaF0mj/kItwgeaDOkAWYfdhe+f2KXyvU67zJhVjz7wOsi4dGAm9Al
	Y2mxUEsyaWXWbo8Q862uPmNMl8gbtzdkuQVajHKilZ83+coW6hULF1Rt19Q2wFA799K7
	fxbw==
X-Gm-Message-State: ALoCoQnue2Dv3RP/5KOFZf7117VdmdhzJ9EtMte6YWHqO9mplcaH9/1/NVY+YeTy6T8kSXNmjq6/
X-Received: by 10.194.179.166 with SMTP id dh6mr724305wjc.87.1423174058967;
	Thu, 05 Feb 2015 14:07:38 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.37.137 with HTTP; Thu, 5 Feb 2015 14:07:18 -0800 (PST)
X-Originating-IP: [166.170.38.32]
In-Reply-To: <6AEDF3C4-DEE0-4E31-83D0-4FD92B125452@voskuil.org>
References: <CABdy8DKS4arkkCLGC=66SUJm5Ugib1EWP7B6MkQRX1k-yd3WBw@mail.gmail.com>
	<CANEZrP3v=ySS4gragaWuBMWi_swocRRRq_kw2edo6+9kifgrFQ@mail.gmail.com>
	<54D3D636.1030308@voskuil.org>
	<CANEZrP3ekWQWeV=Yw_E=n0grORBLHaXLUh3w0EFQdz=HsjWvZw@mail.gmail.com>
	<279489A5-1E46-48A2-8F58-1A25821D4D96@gmail.com>
	<CANEZrP3VAWajxE=mNxb6sLSQbhaQHD=2TgRKvYrEax2PAzCi2A@mail.gmail.com>
	<6AEDF3C4-DEE0-4E31-83D0-4FD92B125452@voskuil.org>
From: Paul Puey <paul@airbitz.co>
Date: Thu, 5 Feb 2015 14:07:18 -0800
Message-ID: <CABdy8DLRGyy5dvmVb_B3vao7Qwz-zdAC3-+2nJkg9rSsU6FLbw@mail.gmail.com>
To: Eric Voskuil <eric@voskuil.org>
Content-Type: multipart/alternative; boundary=089e01419d803d1a39050e5e8814
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
	0.0 T_REMOTE_IMAGE         Message contains an external image
X-Headers-End: 1YJUaP-0008TX-5h
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal for P2P Wireless (Bluetooth LE)
 transfer of Payment URI
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 05 Feb 2015 22:07:46 -0000

--089e01419d803d1a39050e5e8814
Content-Type: text/plain; charset=UTF-8

So if you picked up the BLE broadcast request. All you know is that
*someone* within 100m is requesting bitcoin at a certain address. Not
necessarily who. The *name* is both optional, and possibly just a *handle*
of the user. If I'm sitting 5 ft away from someone at dinner and wanted to
pay them via BLE, I might see "Monkey Dude" on my list and simply ask him
"is that you?" If so, I send it. If there are two "Monkey Dude's" Then I
have to bother with the address prefix, but not otherwise.


[image: logo]
*Paul Puey* CEO / Co-Founder, Airbitz Inc
+1-619-850-8624 | http://airbitz.co | San Diego
<http://facebook.com/airbitz>  <http://twitter.com/airbitz>
<https://plus.google.com/118173667510609425617>
<https://go.airbitz.co/comments/feed/>  <http://linkedin.com/in/paulpuey>
<https://angel.co/paul-puey>
*DOWNLOAD THE AIRBITZ WALLET:*
  <https://play.google.com/store/apps/details?id=com.airbitz>
<https://itunes.apple.com/us/app/airbitz/id843536046>




On Thu, Feb 5, 2015 at 1:46 PM, Eric Voskuil <eric@voskuil.org> wrote:

> BLE has an advertised range of over 100m.
>
> http://www.bluetooth.com/Pages/low-energy-tech-info.aspx
>
> In the case of mass surveillance that range could most likely be extended
> dramatically by the reviewer. I've seen  WiFi ranges of over a mile with a
> strong (not FCC approved) receiver.
>
> WiFi hotspots don't have strong identity or a guaranteed position, so they
> can't be trusted for location.
>
> e
>
> On Feb 5, 2015, at 1:36 PM, Mike Hearn <mike@plan99.net> wrote:
>
> This sounds horrible. You could basically monitor anyone with a wallet in
>> a highly populated area and track them super easily by doing facial
>> recognition.
>>
>
> We're talking about BLE, still? The radio tech that runs in the so called
> "junk bands" because propagation is so poor?
>
> My watch loses its connection to my phone if I just put it down and walk
> around my apartment. I'm all for reasonable paranoia, but Bluetooth isn't
> going to be enabling mass surveillance any time soon. It barely goes
> through air, let alone walls.
>
> Anyway, whatever. I'm just bouncing around ideas for faster user
> interfaces. You could always switch it off or set it to be triggered by the
> presence of particular wifi hotspots, if you don't mind an initial bit of
> setup.
>
> Back on topic - the debate is interesting, but I think to get this to the
> stage of being a BIP we'd need at least another wallet to implement it?
> Then I guess a BIP would be useful regardless of the design issues. The
> prefix matching still feels flaky to me but it's hard to know if you could
> really swipe payments out of the air in practice, without actually trying
> it.
>
>
>

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

<div dir=3D"ltr">So if you picked up the BLE broadcast request. All you kno=
w is that *someone* within 100m is requesting bitcoin at a certain address.=
 Not necessarily who. The *name* is both optional, and possibly just a *han=
dle* of the user. If I&#39;m sitting 5 ft away from someone at dinner and w=
anted to pay them via BLE, I might see &quot;Monkey Dude&quot; on my list a=
nd simply ask him &quot;is that you?&quot; If so, I send it. If there are t=
wo &quot;Monkey Dude&#39;s&quot; Then I have to bother with the address pre=
fix, but not otherwise.</div><div class=3D"gmail_extra"><br clear=3D"all"><=
div><div class=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><=
div><div dir=3D"ltr"><div><div dir=3D"ltr"><div dir=3D"ltr"><br><table bord=
er=3D"0" style=3D"font-size:medium;font-family:Helvetica,Arial,sans-serif">=
<tbody><tr valign=3D"top"><td style=3D"width:auto;vertical-align:top;white-=
space:nowrap"><img src=3D"https://s3.amazonaws.com/webapp.wisestamp.com/v7Z=
g7GfIQ9mF5xlHZrZA_airbitzlogo.png" alt=3D"logo" style=3D"border:none;border=
-top-left-radius:4px;border-top-right-radius:4px;border-bottom-right-radius=
:4px;border-bottom-left-radius:4px">=C2=A0<span style=3D"font-size:small">=
=C2=A0=C2=A0<br></span></td><td><span style=3D"font-size:small"><font color=
=3D"#3d85c6"><b>Paul Puey</b></font><font color=3D"#808080">=C2=A0</font><s=
pan style=3D"color:rgb(136,136,136)">CEO / Co-Founder</span><span style=3D"=
color:rgb(136,136,136)">, Airbitz Inc</span></span><br><div style=3D"margin=
-top:0px;margin-bottom:0px"><span style=3D"font-size:small"><span style=3D"=
color:rgb(128,128,128)"><a style=3D"color:rgb(128,128,128);outline:none;tex=
t-decoration:none">+1-6</a>19-850-8624=C2=A0</span></span><span style=3D"fo=
nt-size:small"><span style=3D"color:rgb(69,102,142)">|=C2=A0</span><a href=
=3D"http://airbitz.co/" style=3D"color:rgb(128,128,128);outline:none" targe=
t=3D"_blank">http://airbitz.co</a></span><span style=3D"font-size:small;col=
or:rgb(128,128,128)">=C2=A0</span><span style=3D"font-size:small;color:rgb(=
128,128,128)"><span style=3D"color:rgb(69,102,142)">|=C2=A0</span>San Diego=
</span></div><div style=3D"margin-top:5px"><a href=3D"http://facebook.com/a=
irbitz" style=3D"color:rgb(17,85,204);outline:none" target=3D"_blank"><img =
src=3D"http://images.wisestamp.com/facebook.png" width=3D"16" style=3D"bord=
er:none"></a>=C2=A0<a href=3D"http://twitter.com/airbitz" style=3D"color:rg=
b(17,85,204);outline:none" target=3D"_blank"><img src=3D"http://images.wise=
stamp.com/twitter.png" width=3D"16" alt=3D"" style=3D"border:none"></a>=C2=
=A0<a href=3D"https://plus.google.com/118173667510609425617" style=3D"color=
:rgb(17,85,204);outline:none" target=3D"_blank"><img src=3D"http://images.w=
isestamp.com/googleplus.png" width=3D"16" style=3D"border:none"></a>=C2=A0<=
a href=3D"https://go.airbitz.co/comments/feed/" style=3D"color:rgb(17,85,20=
4);outline:none" target=3D"_blank"><img src=3D"http://images.wisestamp.com/=
blogRSS.png" width=3D"16" style=3D"border:none"></a>=C2=A0<a href=3D"http:/=
/linkedin.com/in/paulpuey" style=3D"color:rgb(17,85,204);outline:none" targ=
et=3D"_blank"><img src=3D"http://images.wisestamp.com/linkedin.png" width=
=3D"16" style=3D"border:none" alt=3D""></a>=C2=A0<a href=3D"https://angel.c=
o/paul-puey" style=3D"color:rgb(17,85,204);outline:none" target=3D"_blank">=
<img src=3D"http://images.wisestamp.com/angelList.png" width=3D"16" style=
=3D"border:none" alt=3D""></a></div></td></tr></tbody></table><div style=3D=
"font-size:14px;margin-bottom:4px;font-family:Helvetica,Arial,sans-serif;fo=
nt-weight:bold"><b style=3D"font-size:x-small;font-family:arial,sans-serif"=
>DOWNLOAD THE AIRBITZ WALLET:</b><br></div><span style=3D"font-size:medium;=
font-family:Helvetica,Arial,sans-serif"><a href=3D"https://play.google.com/=
store/apps/details?id=3Dcom.airbitz" style=3D"color:rgb(17,85,204);outline:=
none;text-decoration:none" target=3D"_blank"><img src=3D"http://images.wise=
stamp.com.s3.amazonaws.com/apps/mobile_android.png" style=3D"border:none">=
=C2=A0</a></span><span style=3D"font-size:medium;font-family:Helvetica,Aria=
l,sans-serif"></span><span style=3D"font-size:medium;font-family:Helvetica,=
Arial,sans-serif"><a href=3D"https://itunes.apple.com/us/app/airbitz/id8435=
36046" style=3D"color:rgb(17,85,204);outline:none;text-decoration:none" tar=
get=3D"_blank"><img src=3D"http://images.wisestamp.com.s3.amazonaws.com/app=
s/mobile_iphone.png" style=3D"border:none"></a></span><br></div><div dir=3D=
"ltr"><br></div><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><br></di=
v></div><div dir=3D"ltr"><br></div></div></div></div></div></div></div></di=
v></div></div></div>
<br><div class=3D"gmail_quote">On Thu, Feb 5, 2015 at 1:46 PM, Eric Voskuil=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:eric@voskuil.org" target=3D"_blank=
">eric@voskuil.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
<div dir=3D"auto"><div>BLE has an advertised range of over 100m.=C2=A0</div=
><div><br></div><div><a href=3D"http://www.bluetooth.com/Pages/low-energy-t=
ech-info.aspx" target=3D"_blank">http://www.bluetooth.com/Pages/low-energy-=
tech-info.aspx</a><br><br><span style=3D"background-color:rgba(255,255,255,=
0)">In the case of mass surveillance that range could most likely be extend=
ed dramatically by the reviewer. I&#39;ve seen =C2=A0WiFi ranges of over a =
mile with a strong (not FCC approved) receiver.</span></div><div><span styl=
e=3D"background-color:rgba(255,255,255,0)"><br></span></div><div>WiFi hotsp=
ots don&#39;t have strong identity or a guaranteed position, so they can&#3=
9;t be trusted for location.</div><div><span style=3D"background-color:rgba=
(255,255,255,0)"><br></span></div><div><span style=3D"background-color:rgba=
(255,255,255,0)">e</span></div><div><br>On Feb 5, 2015, at 1:36 PM, Mike He=
arn &lt;<a href=3D"mailto:mike@plan99.net" target=3D"_blank">mike@plan99.ne=
t</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div><div dir=3D"lt=
r"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><div dir=3D"auto"><div>This sounds horrible. You could basica=
lly monitor anyone with a wallet in a highly populated area and track them =
super easily by doing facial recognition.</div></div></blockquote><div><br>=
</div><div>We&#39;re talking about BLE, still? The radio tech that runs in =
the so called &quot;junk bands&quot; because propagation is so poor?</div><=
div><br></div><div>My watch loses its connection to my phone if I just put =
it down and walk around my apartment. I&#39;m all for reasonable paranoia, =
but Bluetooth isn&#39;t going to be enabling mass surveillance any time soo=
n. It barely goes through air, let alone walls.</div><div><br></div><div>An=
yway, whatever. I&#39;m just bouncing around ideas for faster user interfac=
es. You could always switch it off or set it to be triggered by the presenc=
e of particular wifi hotspots, if you don&#39;t mind an initial bit of setu=
p.</div><div><br></div><div>Back on topic - the debate is interesting, but =
I think to get this to the stage of being a BIP we&#39;d need at least anot=
her wallet to implement it? Then I guess a BIP would be useful regardless o=
f the design issues. The prefix matching still feels flaky to me but it&#39=
;s hard to know if you could really swipe payments out of the air in practi=
ce, without actually trying it.</div><div><br></div><div><br></div></div></=
div></div>
</div></blockquote></div></blockquote></div><br></div>

--089e01419d803d1a39050e5e8814--