summaryrefslogtreecommitdiff
path: root/57/0a02a8a244f747a1531e5256b7b72532bb9ef3
blob: 48f5c022bbe518a9d3217c46a07207ee6aab9caa (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
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <paul@airbitz.co>) id 1YJSht-0001l8-AA
	for bitcoin-development@lists.sourceforge.net;
	Thu, 05 Feb 2015 20:07:21 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of airbitz.co
	designates 209.85.212.177 as permitted sender)
	client-ip=209.85.212.177; envelope-from=paul@airbitz.co;
	helo=mail-wi0-f177.google.com; 
Received: from mail-wi0-f177.google.com ([209.85.212.177])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1YJShm-0002t8-4o
	for bitcoin-development@lists.sourceforge.net;
	Thu, 05 Feb 2015 20:07:21 +0000
Received: by mail-wi0-f177.google.com with SMTP id r20so207444wiv.4
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 05 Feb 2015 12:07:08 -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:from:date:message-id:subject:to
	:content-type;
	bh=kUPGHNzPrQTGUCYb8Aj5SeBENTOwQIZCfPdHL/F+PbY=;
	b=a+VsLcoC2j5bWiNg033Gm6Vn0sHiF8Zufi3pQg+y0vKVvU+MJLIWcQ7upusDqYXWO2
	Jgt5YQutiPI0NgG0qr3gqoCpVMTAoWN0JOBIMRE1Q3AeJkmhunFi5A2AElQuZDdtDOmJ
	BFYUxgczeDFxJ8dwKXGvB9npL2VEBbV3icMY0qbZgdowD1XJqN6U2qAfu5//JNSXF7ap
	yL5jiu/q21ONhbuFh4lqNHSeiOhCwZXGKIZRS83B8ZObrOdS/paiDOvDP1dAasyG5vgu
	ssybGP24/l1JMSPncaBGecRLGxr3zcSM/PIbM2VUqNlG+qmFRzUZ5MJvorEb8s3uA1tg
	h9Eg==
X-Gm-Message-State: ALoCoQlRCn44YPvX5+3QBPCvcsk3/ToPMCi0paaS0bhakU45O4QuJh7uSB0idlChABERHpPKwmfB
X-Received: by 10.180.228.72 with SMTP id sg8mr376137wic.48.1423166827905;
	Thu, 05 Feb 2015 12:07:07 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.37.137 with HTTP; Thu, 5 Feb 2015 12:06:47 -0800 (PST)
X-Originating-IP: [64.245.0.218]
From: Paul Puey <paul@airbitz.co>
Date: Thu, 5 Feb 2015 12:06:47 -0800
Message-ID: <CABdy8DKS4arkkCLGC=66SUJm5Ugib1EWP7B6MkQRX1k-yd3WBw@mail.gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=001a1134cc4e3bf87b050e5cd90c
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: 1YJShm-0002t8-4o
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:07:21 -0000

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

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.

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

<div dir=3D"ltr">The BIP70 protocol would preclude individuals from utilizi=
ng 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 recipien=
t (who would still need internet to verify the Tx). This is an important us=
e case for areas with poor 3G/4G connectivity as I&#39;ve experience myself=
.<div><br></div><div>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 p=
ayment 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&#39;ll lo=
ok at adding this to the Motivation section.</div><div><div><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 border=3D"0" sty=
le=3D"font-size:medium;font-family:Helvetica,Arial,sans-serif"><tbody><tr v=
align=3D"top"><td style=3D"width:auto;vertical-align:top;white-space:nowrap=
"><img src=3D"https://s3.amazonaws.com/webapp.wisestamp.com/v7Zg7GfIQ9mF5xl=
HZrZA_airbitzlogo.png" alt=3D"logo" style=3D"border: none; border-radius: 4=
px;">=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></f=
ont><font color=3D"#808080">=C2=A0</font><span style=3D"color:rgb(136,136,1=
36)">CEO / Co-Founder</span><span style=3D"color:rgb(136,136,136)">, Airbit=
z Inc</span></span><br><div style=3D"margin-top:0px;margin-bottom:0px"><spa=
n 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-85=
0-8624=C2=A0</span></span><span style=3D"font-size:small"><span style=3D"co=
lor: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://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"colo=
r: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.wisestamp.co=
m/facebook.png" width=3D"16" style=3D"border: none;"></a>=C2=A0<a href=3D"h=
ttp://twitter.com/airbitz" style=3D"color:rgb(17,85,204);outline:none" targ=
et=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://plus.goo=
gle.com/118173667510609425617" style=3D"color:rgb(17,85,204);outline:none" =
target=3D"_blank"><img src=3D"http://images.wisestamp.com/googleplus.png" w=
idth=3D"16" style=3D"border: none;"></a>=C2=A0<a href=3D"https://go.airbitz=
.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"16" st=
yle=3D"border: none;"></a>=C2=A0<a href=3D"http://linkedin.com/in/paulpuey"=
 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: non=
e;" alt=3D""></a>=C2=A0<a href=3D"https://angel.co/paul-puey" style=3D"colo=
r: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-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 =
style=3D"font-size:medium;font-family:Helvetica,Arial,sans-serif"></span><s=
pan style=3D"font-size:medium;font-family:Helvetica,Arial,sans-serif"><a hr=
ef=3D"https://itunes.apple.com/us/app/airbitz/id843536046" style=3D"color:r=
gb(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 =
dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><br></div></div><div dir=3D"l=
tr"><table id=3D"msg33351988" style=3D"margin:0px 0px 20px 10px;padding:0px=
;border:0px;outline:0px;font-size:13px;vertical-align:baseline;border-colla=
pse:collapse;border-spacing:0px;width:765px;color:rgb(85,85,85);font-family=
:sans-serif;line-height:18px;background-image:initial;background-repeat:ini=
tial"><tbody style=3D"margin:0px;padding:0px;border:0px;outline:0px;vertica=
l-align:baseline;background:transparent"><tr style=3D"margin:0px;padding:0p=
x;border:0px;outline:0px;vertical-align:baseline;background:transparent"><t=
d class=3D"" style=3D"padding:5px 10px;border-width:0px 0px 1px;border-bott=
om-style:solid;border-bottom-color:rgb(229,229,229);outline:0px;vertical-al=
ign:middle;white-space:nowrap;background:rgb(221,221,221)"><div style=3D"ma=
rgin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline;backgro=
und:transparent"><small style=3D"margin:0px;padding:0px;border:0px;outline:=
0px;font-size:11.0500001907349px;vertical-align:baseline;background:transpa=
rent">From: Andreas Schildbach &lt;andreas@sc...&gt; - 2015-02-05 13:47:04<=
/small><div class=3D"" style=3D"margin:0px;padding:0px;border:0px;outline:0=
px;vertical-align:baseline;background:transparent"><small style=3D"margin:0=
px;padding:0px;border:0px;outline:0px;font-size:11.0500001907349px;vertical=
-align:baseline;background:transparent"></small></div></div></td></tr><tr s=
tyle=3D"margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseli=
ne;background:transparent"><td class=3D"" style=3D"padding:5px 10px;border-=
width:0px 0px 1px;border-bottom-style:solid;border-bottom-color:rgb(229,229=
,229);outline:0px;vertical-align:middle;background:transparent"><pre style=
=3D"margin-top:0px;margin-bottom:0px;padding:15px;border-width:0px 0px 0px =
1px;border-left-style:solid;border-left-color:rgb(229,229,229);outline:0px;=
vertical-align:baseline;font-family:monospace,sans-serif;white-space:pre-wr=
ap;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>

--001a1134cc4e3bf87b050e5cd90c--