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
|
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 <alexy.kot.all@gmail.com>) id 1WQgzq-0006Op-LM
for bitcoin-development@lists.sourceforge.net;
Thu, 20 Mar 2014 17:43:14 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.128.170 as permitted sender)
client-ip=209.85.128.170; envelope-from=alexy.kot.all@gmail.com;
helo=mail-ve0-f170.google.com;
Received: from mail-ve0-f170.google.com ([209.85.128.170])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WQgzo-0000hg-D5
for bitcoin-development@lists.sourceforge.net;
Thu, 20 Mar 2014 17:43:14 +0000
Received: by mail-ve0-f170.google.com with SMTP id pa12so1345006veb.1
for <bitcoin-development@lists.sourceforge.net>;
Thu, 20 Mar 2014 10:43:07 -0700 (PDT)
X-Received: by 10.221.29.196 with SMTP id rz4mr34734712vcb.8.1395337386931;
Thu, 20 Mar 2014 10:43:06 -0700 (PDT)
MIME-Version: 1.0
Sender: alexy.kot.all@gmail.com
Received: by 10.59.0.38 with HTTP; Thu, 20 Mar 2014 10:42:26 -0700 (PDT)
In-Reply-To: <CAJHLa0NeFdXzioQrmK6iKzr85pL3vvTAQH2_vKM3M+T+ZWYjgQ@mail.gmail.com>
References: <lc5hmg$1jh$1@ger.gmane.org> <leuunm$tjk$1@ger.gmane.org>
<CANEZrP3nQfvDArKTRgje0Cus4G2JD_zpxSjA3fXfxM2TNAP80Q@mail.gmail.com>
<CALDj+BafD+6KTNcYDBEu5gNPzYozSkiC-JCxrY-PzXL2DYBRsw@mail.gmail.com>
<CAJHLa0N4J_Z907+D0ENSNKfNAW2N=7Jf4JzSCO=SU558GtGTzA@mail.gmail.com>
<lge7nk$3mf$2@ger.gmane.org>
<CANEZrP0J849oDvMWjf8LWi0xj44Q8DaUwDip5_smVBMNgeQ3mw@mail.gmail.com>
<20140320121221.GA25052@netbook.cypherspace.org>
<CAJHLa0NeFdXzioQrmK6iKzr85pL3vvTAQH2_vKM3M+T+ZWYjgQ@mail.gmail.com>
From: Alex Kotenko <alexykot@gmail.com>
Date: Thu, 20 Mar 2014 17:42:26 +0000
X-Google-Sender-Auth: dCNi55jPCnLaS-az1Lu6CngrgX8
Message-ID: <CALDj+BbF5=L88n6VvDt=ctnr+_1730L3RN+3nb2N3AW3RLESRg@mail.gmail.com>
To: Jeff Garzik <jgarzik@bitpay.com>
Content-Type: multipart/alternative; boundary=001a1133a1c04a3db304f50d4de3
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(alexy.kot.all[at]gmail.com)
-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
X-Headers-End: 1WQgzo-0000hg-D5
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
Andreas Schildbach <andreas@schildbach.de>
Subject: Re: [Bitcoin-development] Payment Protocol for Face-to-face Payments
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, 20 Mar 2014 17:43:14 -0000
--001a1133a1c04a3db304f50d4de3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
2014-03-20 17:31 GMT+00:00 Jeff Garzik <jgarzik@bitpay.com>:
> On Thu, Mar 20, 2014 at 8:12 AM, Adam Back <adam@cypherspace.org> wrote:
> > Whats a sensible limit on practical/convenient QR code size?
>
> Extremely limited. Preferably under 100 bytes. You will see
> increasingly poor operating in varying light conditions, such as
> paying via QR code on a printed receipt in a pub at night. That was
> one of the motivations for BIP 73.
>
=E2=80=8BHmm, in this case I think base43 discussion is irrelevant. Even wi=
th best
space utilization we can get =E2=80=8Bwe will not be able to fit in anythin=
g bigger
than a smallest unsigned payment certificate. And that is not so useful. So
probably we should stick with BIP73 approach and bluetooth URI scheme we're
inventing.
>
>
> On Thu, Mar 20, 2014 at 4:09 AM, Andreas Schildbach
> <andreas@schildbach.de> wrote:
> > Afaik, BIP73 needs an external server (the web server).
>
> Yes. Internet connectivity is not a rarity these days. Near-field
> web servers also work fine.
>
> --
> Jeff Garzik
> Bitcoin core developer and open source evangelist
> BitPay, Inc. https://bitpay.com/
>
>
> -------------------------------------------------------------------------=
-----
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and thei=
r
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--001a1133a1c04a3db304f50d4de3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:courier =
new,monospace;color:#003300"><span style=3D"font-family:arial;color:rgb(34,=
34,34)">2014-03-20 17:31 GMT+00:00 Jeff Garzik </span><span dir=3D"ltr" sty=
le=3D"font-family:arial;color:rgb(34,34,34)"><<a href=3D"mailto:jgarzik@=
bitpay.com" target=3D"_blank">jgarzik@bitpay.com</a>></span><span style=
=3D"font-family:arial;color:rgb(34,34,34)">:</span><br>
</div><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex"><div class=3D"">On Thu, Mar 20, 2014 at 8:12 AM, Adam Back =
<<a href=3D"mailto:adam@cypherspace.org">adam@cypherspace.org</a>> wr=
ote:<br>
> Whats a sensible limit on practical/convenient QR code size?<br>
<br>
</div>Extremely limited. =C2=A0Preferably under 100 bytes. =C2=A0You will s=
ee<br>
increasingly poor operating in varying light conditions, such as<br>
paying via QR code on a printed receipt in a pub at night. =C2=A0That was<b=
r>
one of the motivations for BIP 73.<br></blockquote><div><div class=3D"gmail=
_default" style=3D"font-family:'courier new',monospace;color:rgb(0,=
51,0)">=E2=80=8BHmm, in this case I think base43 discussion is irrelevant. =
Even with best space utilization we can get =E2=80=8Bwe will not be able to=
fit in anything bigger than a smallest unsigned payment certificate. And t=
hat is not so useful. So probably we should stick with BIP73 approach and b=
luetooth URI scheme we're inventing.=C2=A0</div>
<br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=3D""><br>
<br>
On Thu, Mar 20, 2014 at 4:09 AM, Andreas Schildbach<br>
<<a href=3D"mailto:andreas@schildbach.de">andreas@schildbach.de</a>> =
wrote:<br>
> Afaik, BIP73 needs an external server (the web server).<br>
<br>
</div>Yes. =C2=A0Internet connectivity is not a rarity these days. =C2=A0Ne=
ar-field<br>
web servers also work fine.<br>
<div class=3D"im HOEnZb"><br>
--<br>
Jeff Garzik<br>
Bitcoin core developer and open source evangelist<br>
BitPay, Inc. =C2=A0 =C2=A0 =C2=A0<a href=3D"https://bitpay.com/" target=3D"=
_blank">https://bitpay.com/</a><br>
<br>
</div><div class=3D"HOEnZb"><div class=3D"h5">-----------------------------=
-------------------------------------------------<br>
Learn Graph Databases - Download FREE O'Reilly Book<br>
"Graph Databases" is the definitive new guide to graph databases =
and their<br>
applications. Written by three acclaimed leaders in the field,<br>
this first edition is now available. Download your free book today!<br>
<a href=3D"http://p.sf.net/sfu/13534_NeoTech" target=3D"_blank">http://p.sf=
.net/sfu/13534_NeoTech</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@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>
</div></div></blockquote></div><br></div></div>
--001a1133a1c04a3db304f50d4de3--
|
