summaryrefslogtreecommitdiff
path: root/84/aa591902cb6d03a54fc29417c3c7bc3a00547f
blob: 3e2b0a7aba2c8d1932741c876cb171b3f5bba4db (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
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <paul@airbitz.co>) id 1YJTBH-0003pK-4e
	for bitcoin-development@lists.sourceforge.net;
	Thu, 05 Feb 2015 20:37:47 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of airbitz.co
	designates 209.85.212.179 as permitted sender)
	client-ip=209.85.212.179; envelope-from=paul@airbitz.co;
	helo=mail-wi0-f179.google.com; 
Received: from mail-wi0-f179.google.com ([209.85.212.179])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1YJTBE-0003oI-IK
	for bitcoin-development@lists.sourceforge.net;
	Thu, 05 Feb 2015 20:37:43 +0000
Received: by mail-wi0-f179.google.com with SMTP id l15so385192wiw.0
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 05 Feb 2015 12:37:34 -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=DONLSinYyx8MoiYTFM2lejlOchOwVBKmRAjlQPM8peA=;
	b=NgUxMJfTO1zS7UKFq2caXTnWcMzWMhz2iuMe08iwWgYvNao08BjhsQGAEobmYxFonZ
	yFvWM5/8EyBL6xnVNu9GmA58OqBO8Jbezs++fNDgdKFQw8QnXrrvZbpFN2cQl7mJ1CYn
	1xZyFngx8S/Do7x6GJ0rR2MHCAQlnjnn4Nw6FBURCmbQUtNkOtShrAGGhM/cVAyKwofU
	lvooiKDxQL9KbUakGlQH60SnhUdb4DKwUBzAEuLSU1TY5awCZ0Ei2ehTTlSECcAg5KFN
	6JFFF3ssXwlWKu3UuS7rquEAd9J3kZ3Oqx8iKpiE6ri3UegM3ojq9/tqrI6QnNXOHMPr
	4eUg==
X-Gm-Message-State: ALoCoQl8+OiP45oOKyQ/U516B5/F1iGE/LT4hBS8eAQFXAe5DUUvp7NI1wc0vPzroOBMX/kdxVwA
X-Received: by 10.180.20.226 with SMTP id q2mr48834wie.28.1423168654423; Thu,
	05 Feb 2015 12:37:34 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.37.137 with HTTP; Thu, 5 Feb 2015 12:37:14 -0800 (PST)
X-Originating-IP: [64.245.0.218]
In-Reply-To: <CANEZrP3v=ySS4gragaWuBMWi_swocRRRq_kw2edo6+9kifgrFQ@mail.gmail.com>
References: <CABdy8DKS4arkkCLGC=66SUJm5Ugib1EWP7B6MkQRX1k-yd3WBw@mail.gmail.com>
	<CANEZrP3v=ySS4gragaWuBMWi_swocRRRq_kw2edo6+9kifgrFQ@mail.gmail.com>
From: Paul Puey <paul@airbitz.co>
Date: Thu, 5 Feb 2015 12:37:14 -0800
Message-ID: <CABdy8DL0x6_02HCxKMrQWyCDcBXsGr7+0iBt2Ez2a_kGRwjffQ@mail.gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=bcaec53d55ed1a506a050e5d46a7
X-Spam-Score: -0.4 (/)
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.2 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1YJTBE-0003oI-IK
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 20:37:47 -0000

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

Thanks for CC'ing me Mike. Having trouble receiving maillist list posts.

Even if a user could get the BIP70 URL in the URI, they would still need
internet to access the URL. This BLE spec doesn't preclude BIP70, but can
work with it while still allowing individuals without a certificate to
broadcast a request.

The issue of confused payments becomes less so if the Recipient broadcasts
a name along with the 10 digit public addr prefix. Only if there is a name
conflict will the user have to be concerned with the prefix. The name can
be something like

Mikes Coffee #1 and it can have a "Register #1" at the counter. A customer
facing screen can also show the 10 digit prefix.


[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 12:28 PM, Mike Hearn <mike@plan99.net> wrote:

> BIP70 requests can be sent over bluetooth as well, as can transactions.
> Bitcoin Wallet can already send money even when offline by doing this. It's
> transparent to the user. I mean original Bluetooth in this context - BLE
> has incredibly tight data constraints and isn't really meant for data
> transfer.
>
> Yes Android Beam has a pretty stupid UI. You can actually tap the devices,
> take them away and then press, but that's not obvious at all. There have
> been new APIs added in recent releases that give more control over this, so
> it's possible we can revisit things and make the UI better these days.
>
> The donation to live performer example is good - there's no issue of
> accidentally paying for someone else in this context as there's only one
> recipient, but many senders.
>
> The issue of confused payments remains in other situations though.
>
> For the coffee shop use case, it'd be nicer (I think) if we aim for a
> Square-style UI where the device broadcasts a (link to) a photo of the user
> combined with a bluetooth MAC. Then the merchant tablet can show faces of
> people in the shop, and can push a payment request to the users device.
> That device can then buzz the user, show a confirmation screen, put
> something on their smart watch etc or just auto-authorise the payment
> because the BIP70 signature is from a trusted merchant. User never even
> needs to touch their phone at all.
>
> On Thu, Feb 5, 2015 at 9:06 PM, Paul Puey <paul@airbitz.co> wrote:
>
>> The BIP70 protocol would preclude individuals from utilizing the P2P
>> transfer spec. It would also require that a Sender have internet
>> connectivity to get the payment protocol info. BLE could enable payment w/o
>> internet by first transferring the URI to from Recipient to Sender. Then in
>> the future, we could sign a Tx and send it over BLE back to the recipient
>> (who would still need internet to verify the Tx). This is an important use
>> case for areas with poor 3G/4G connectivity as I've experience myself.
>>
>> Also, due to Android issues, NFC is incredibly clunky. The URI Sender is
>> required to tap the screen *while* the two phones are in contact. We
>> support NFC the same way Bitcoin Wallet does, but unless the payment
>> recipient has a custom Android device (which a merchant might) then the
>> usage model is worse than scanning a QR code. BLE also allows people to pay
>> at a distance such as for a donation to a live performer. We'll look at
>> adding this to the Motivation section.
>>
>> [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>
>>
>>
>> From: Andreas Schildbach <andreas@sc...> - 2015-02-05 13:47:04
>>
>> Thanks Paul, for writing up your protocol!
>>
>> First thoughts:
>>
>> For a BIP standard, I think we should skip "bitcoin:" URIs entirely and
>> publish BIP70 payment requests instead. URIs mainly stick around because
>> of QR codes limited capacity. BIP70 would partly address the "copycat"
>> problem by signing payment requests.
>>
>> In your Motivation section, I miss some words about NFC. NFC already
>> addresses all of the usability issues mentioned and is supported by
>> mobile wallets since 2011. That doesn't mean your method doesn't make
>> sense in some situations, but I think it should be explained why to
>> prefer broadcasting payment requests over picking them up via near field
>> radio.
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Dive into the World of Parallel Programming. The Go Parallel Website,
>> sponsored by Intel and developed in partnership with Slashdot Media, is
>> your
>> hub for all things parallel software development, from weekly thought
>> leadership blogs to news, videos, case studies, tutorials and more. Take a
>> look and join the conversation now. http://goparallel.sourceforge.net/
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>>
>

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

<div dir=3D"ltr">Thanks for CC&#39;ing me Mike. Having trouble receiving ma=
illist list posts.<div><br></div><div><span style=3D"font-size:12.800000190=
7349px">Even if a user could get the BIP70 URL in the URI, they would still=
 need internet to access the URL. This BLE spec doesn&#39;t preclude BIP70,=
 but can work with it while still allowing individuals without a certificat=
e to broadcast a request.</span></div><div><span style=3D"font-size:12.8000=
001907349px"><br></span></div><div><span style=3D"font-size:12.800000190734=
9px">The issue of confused payments becomes less so if the Recipient broadc=
asts a name along with the 10 digit public addr prefix. Only if there is a =
name conflict will the user have to be concerned with the prefix. The name =
can be something like=C2=A0</span></div><div><span style=3D"font-size:12.80=
00001907349px"><br></span></div><div><span style=3D"font-size:12.8000001907=
349px">Mikes Coffee #1 and it can have a &quot;Register #1&quot; at the cou=
nter. A customer facing screen can also show the 10 digit prefix.</span></d=
iv><div class=3D"gmail_extra"><br clear=3D"all"><div><div class=3D"gmail_si=
gnature"><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 border=3D"0" style=3D"font-siz=
e: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/v7Zg7GfIQ9mF5xlHZrZA_airbitzl=
ogo.png" alt=3D"logo" style=3D"border:none;border-top-left-radius:4px;borde=
r-top-right-radius:4px;border-bottom-right-radius:4px;border-bottom-left-ra=
dius: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><span style=3D"color:rgb(136,=
136,136)">CEO / Co-Founder</span><span style=3D"color:rgb(136,136,136)">, A=
irbitz 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;text-decoration:none">+1-6</a>=
19-850-8624=C2=A0</span></span><span style=3D"font-size:small"><span style=
=3D"color:rgb(69,102,142)">|=C2=A0</span><a href=3D"http://airbitz.co/" sty=
le=3D"color:rgb(128,128,128);outline:none" target=3D"_blank">http://airbitz=
.co</a></span><span style=3D"font-size:small;color: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/airbitz" style=3D"color:=
rgb(17,85,204);outline:none" target=3D"_blank"><img src=3D"http://images.wi=
sestamp.com/facebook.png" width=3D"16" style=3D"border:none"></a>=C2=A0<a h=
ref=3D"http://twitter.com/airbitz" style=3D"color:rgb(17,85,204);outline:no=
ne" target=3D"_blank"><img src=3D"http://images.wisestamp.com/twitter.png" =
width=3D"16" alt=3D"" style=3D"border:none"></a>=C2=A0<a href=3D"https://pl=
us.google.com/118173667510609425617" style=3D"color:rgb(17,85,204);outline:=
none" target=3D"_blank"><img src=3D"http://images.wisestamp.com/googleplus.=
png" width=3D"16" style=3D"border:none"></a>=C2=A0<a href=3D"https://go.air=
bitz.co/comments/feed/" style=3D"color:rgb(17,85,204);outline:none" target=
=3D"_blank"><img src=3D"http://images.wisestamp.com/blogRSS.png" width=3D"1=
6" style=3D"border:none"></a>=C2=A0<a href=3D"http://linkedin.com/in/paulpu=
ey" style=3D"color:rgb(17,85,204);outline:none" target=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.co/paul-puey" style=3D"co=
lor:rgb(17,85,204);outline:none" target=3D"_blank"><img src=3D"http://image=
s.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-bot=
tom:4px;font-family:Helvetica,Arial,sans-serif;font-weight:bold"><b style=
=3D"font-size:x-small;font-family:arial,sans-serif">DOWNLOAD THE AIRBITZ WA=
LLET:</b><br></div><span style=3D"font-size:medium;font-family:Helvetica,Ar=
ial,sans-serif"><a href=3D"https://play.google.com/store/apps/details?id=3D=
com.airbitz" style=3D"color:rgb(17,85,204);outline:none;text-decoration:non=
e" target=3D"_blank"><img src=3D"http://images.wisestamp.com.s3.amazonaws.c=
om/apps/mobile_android.png" style=3D"border:none">=C2=A0</a></span><span st=
yle=3D"font-size:medium;font-family:Helvetica,Arial,sans-serif"></span><spa=
n style=3D"font-size:medium;font-family:Helvetica,Arial,sans-serif"><a href=
=3D"https://itunes.apple.com/us/app/airbitz/id843536046" style=3D"color:rgb=
(17,85,204);outline:none;text-decoration:none" target=3D"_blank"><img src=
=3D"http://images.wisestamp.com.s3.amazonaws.com/apps/mobile_iphone.png" st=
yle=3D"border:none"></a></span><br></div><div dir=3D"ltr"><br></div><div di=
r=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><br></div></div><div dir=3D"ltr=
"><br></div></div></div></div></div></div></div></div></div></div></div>
<br><div class=3D"gmail_quote">On Thu, Feb 5, 2015 at 12:28 PM, Mike Hearn =
<span dir=3D"ltr">&lt;<a href=3D"mailto:mike@plan99.net" target=3D"_blank">=
mike@plan99.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><di=
v dir=3D"ltr"><div class=3D"gmail_extra">BIP70 requests can be sent over bl=
uetooth as well, as can transactions. Bitcoin Wallet can already send money=
 even when offline by doing this. It&#39;s transparent to the user. I mean =
original Bluetooth in this context - BLE has incredibly tight data constrai=
nts and isn&#39;t really meant for data transfer.</div><div class=3D"gmail_=
extra"><br></div><div class=3D"gmail_extra">Yes Android Beam has a pretty s=
tupid UI. You can actually tap the devices, take them away and then press, =
but that&#39;s not obvious at all. There have been new APIs added in recent=
 releases that give more control over this, so it&#39;s possible we can rev=
isit things and make the UI better these days.</div><div class=3D"gmail_ext=
ra"><br></div><div class=3D"gmail_extra">The donation to live performer exa=
mple is good - there&#39;s no issue of accidentally paying for someone else=
 in this context as there&#39;s only one recipient, but many senders.</div>=
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">The issue o=
f confused payments remains in other situations though.</div><div class=3D"=
gmail_extra"><br></div><div class=3D"gmail_extra">For the coffee shop use c=
ase, it&#39;d be nicer (I think) if we aim for a Square-style UI where the =
device broadcasts a (link to) a photo of the user combined with a bluetooth=
 MAC. Then the merchant tablet can show faces of people in the shop, and ca=
n push a payment request to the users device. That device can then buzz the=
 user, show a confirmation screen, put something on their smart watch etc o=
r just auto-authorise the payment because the BIP70 signature is from a tru=
sted merchant. User never even needs to touch their phone at all.</div><div=
 class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><div class=3D"g=
mail_quote">On Thu, Feb 5, 2015 at 9:06 PM, Paul Puey <span dir=3D"ltr">&lt=
;<a href=3D"mailto:paul@airbitz.co" target=3D"_blank">paul@airbitz.co</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">The BIP=
70 protocol would preclude individuals from utilizing the P2P transfer spec=
. It would also require that a Sender have internet connectivity to get the=
 payment protocol info. BLE could enable payment w/o internet by first tran=
sferring the URI to from Recipient to Sender. Then in the future, we could =
sign a Tx and send it over BLE back to the recipient (who would still need =
internet to verify the Tx). This is an important use case for areas with po=
or 3G/4G connectivity as I&#39;ve experience myself.<div><br></div><div>Als=
o, due to Android issues, NFC is incredibly clunky. The URI Sender is requi=
red to tap the screen *while* the two phones are in contact. We support NFC=
 the same way Bitcoin Wallet does, but unless the payment recipient has a c=
ustom Android device (which a merchant might) then the usage model is worse=
 than scanning a QR code. BLE also allows people to pay at a distance such =
as for a donation to a live performer. We&#39;ll look at adding this to the=
 Motivation section.</div><div><div><div><div><div dir=3D"ltr"><div><div di=
r=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><span><div dir=3D"ltr=
"><br><table border=3D"0" style=3D"font-size:medium;font-family:Helvetica,A=
rial,sans-serif"><tbody><tr valign=3D"top"><td style=3D"width:auto;vertical=
-align:top;white-space:nowrap"><img alt=3D"logo" style=3D"border:none;borde=
r-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 Pu=
ey</b></font><font color=3D"#808080">=C2=A0</font><span 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;text-decoration:none">+1-6=
</a>19-850-8624=C2=A0</span></span><span style=3D"font-size:small"><span st=
yle=3D"color:rgb(69,102,142)">|=C2=A0</span><a href=3D"http://airbitz.co/" =
style=3D"color:rgb(128,128,128);outline:none" target=3D"_blank">http://airb=
itz.co</a></span><span style=3D"font-size:small;color:rgb(128,128,128)">=C2=
=A0</span><span style=3D"font-size:small;color:rgb(128,128,128)"><span styl=
e=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/airbitz" style=3D"color:=
rgb(17,85,204);outline:none" target=3D"_blank"><img width=3D"16" style=3D"b=
order:none"></a>=C2=A0<a href=3D"http://twitter.com/airbitz" style=3D"color=
:rgb(17,85,204);outline:none" target=3D"_blank"><img width=3D"16" alt=3D"" =
style=3D"border:none"></a>=C2=A0<a href=3D"https://plus.google.com/11817366=
7510609425617" style=3D"color:rgb(17,85,204);outline:none" target=3D"_blank=
"><img width=3D"16" style=3D"border:none"></a>=C2=A0<a href=3D"https://go.a=
irbitz.co/comments/feed/" style=3D"color:rgb(17,85,204);outline:none" targe=
t=3D"_blank"><img width=3D"16" style=3D"border:none"></a>=C2=A0<a href=3D"h=
ttp://linkedin.com/in/paulpuey" style=3D"color:rgb(17,85,204);outline:none"=
 target=3D"_blank"><img width=3D"16" style=3D"border:none" alt=3D""></a>=C2=
=A0<a href=3D"https://angel.co/paul-puey" style=3D"color:rgb(17,85,204);out=
line:none" target=3D"_blank"><img 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;font-weight:bold"><b styl=
e=3D"font-size:x-small;font-family:arial,sans-serif">DOWNLOAD THE AIRBITZ W=
ALLET:</b><br></div><span style=3D"font-size:medium;font-family:Helvetica,A=
rial,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 style=3D"border:none">=C2=A0</a></span><span s=
tyle=3D"font-size:medium;font-family:Helvetica,Arial,sans-serif"></span><sp=
an style=3D"font-size:medium;font-family:Helvetica,Arial,sans-serif"><a hre=
f=3D"https://itunes.apple.com/us/app/airbitz/id843536046" style=3D"color:rg=
b(17,85,204);outline:none;text-decoration:none" target=3D"_blank"><img styl=
e=3D"border:none"></a></span><br></div><div dir=3D"ltr"><br></div></span><d=
iv dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><br></div></div><div dir=
=3D"ltr"><table style=3D"margin:0px 0px 20px 10px;padding:0px;border:0px;ou=
tline:0px;font-size:13px;vertical-align:baseline;border-collapse:collapse;b=
order-spacing:0px;width:765px;color:rgb(85,85,85);font-family:sans-serif;li=
ne-height:18px;background-image:initial;background-repeat:initial"><tbody s=
tyle=3D"margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseli=
ne;background:transparent"><tr style=3D"margin:0px;padding:0px;border:0px;o=
utline:0px;vertical-align:baseline;background:transparent"><td style=3D"pad=
ding:5px 10px;border-width:0px 0px 1px;border-bottom-style:solid;border-bot=
tom-color:rgb(229,229,229);outline:0px;vertical-align:middle;white-space:no=
wrap;background:rgb(221,221,221)"><div style=3D"margin:0px;padding:0px;bord=
er:0px;outline:0px;vertical-align:baseline;background:transparent"><small s=
tyle=3D"margin:0px;padding:0px;border:0px;outline:0px;font-size:11.05000019=
07349px;vertical-align:baseline;background:transparent">From: Andreas Schil=
dbach &lt;andreas@sc...&gt; - 2015-02-05 13:47:04</small><div style=3D"marg=
in:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline;backgroun=
d:transparent"><small style=3D"margin:0px;padding:0px;border:0px;outline:0p=
x;font-size:11.0500001907349px;vertical-align:baseline;background:transpare=
nt"></small></div></div></td></tr><tr style=3D"margin:0px;padding:0px;borde=
r:0px;outline:0px;vertical-align:baseline;background:transparent"><td style=
=3D"padding:5px 10px;border-width:0px 0px 1px;border-bottom-style:solid;bor=
der-bottom-color:rgb(229,229,229);outline:0px;vertical-align:middle;backgro=
und:transparent"><pre style=3D"margin-top:0px;margin-bottom:0px;padding:15p=
x;border-width:0px 0px 0px 1px;border-left-style:solid;border-left-color:rg=
b(229,229,229);outline:0px;vertical-align:baseline;font-family:monospace,sa=
ns-serif;white-space:pre-wrap;word-wrap:break-word;overflow:auto;background=
:transparent">Thanks Paul, for writing up your protocol!

First thoughts:

For a BIP standard, I think we should skip &quot;bitcoin:&quot; URIs entire=
ly and
publish BIP70 payment requests instead. URIs mainly stick around because
of QR codes limited capacity. BIP70 would partly address the &quot;copycat&=
quot;
problem by signing payment requests.

In your Motivation section, I miss some words about NFC. NFC already
addresses all of the usability issues mentioned and is supported by
mobile wallets since 2011. That doesn&#39;t mean your method doesn&#39;t ma=
ke
sense in some situations, but I think it should be explained why to
prefer broadcasting payment requests over picking them up via near field
radio.
</pre><div><br></div></td></tr></tbody></table></div></div></div></div></di=
v></div></div></div></div></div></div>
</div></div></div>
<br>-----------------------------------------------------------------------=
-------<br>
Dive into the World of Parallel Programming. The Go Parallel Website,<br>
sponsored by Intel and developed in partnership with Slashdot Media, is you=
r<br>
hub for all things parallel software development, from weekly thought<br>
leadership blogs to news, videos, case studies, tutorials and more. Take a<=
br>
look and join the conversation now. <a href=3D"http://goparallel.sourceforg=
e.net/" target=3D"_blank">http://goparallel.sourceforge.net/</a><br>_______=
________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net" target=3D"_bla=
nk">Bitcoin-development@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div><br></div></div>
</blockquote></div><br></div></div>

--bcaec53d55ed1a506a050e5d46a7--