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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <alexy.kot.all@gmail.com>) id 1WN6Bm-00049n-8y
for bitcoin-development@lists.sourceforge.net;
Mon, 10 Mar 2014 19:48:42 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.176 as permitted sender)
client-ip=209.85.220.176; envelope-from=alexy.kot.all@gmail.com;
helo=mail-vc0-f176.google.com;
Received: from mail-vc0-f176.google.com ([209.85.220.176])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WN6Bl-0003LS-7E
for bitcoin-development@lists.sourceforge.net;
Mon, 10 Mar 2014 19:48:42 +0000
Received: by mail-vc0-f176.google.com with SMTP id lc6so7042867vcb.35
for <bitcoin-development@lists.sourceforge.net>;
Mon, 10 Mar 2014 12:48:35 -0700 (PDT)
X-Received: by 10.58.220.161 with SMTP id px1mr24845625vec.13.1394480915700;
Mon, 10 Mar 2014 12:48:35 -0700 (PDT)
MIME-Version: 1.0
Sender: alexy.kot.all@gmail.com
Received: by 10.59.0.38 with HTTP; Mon, 10 Mar 2014 12:47:55 -0700 (PDT)
In-Reply-To: <lfl3p6$na3$1@ger.gmane.org>
References: <CANEZrP3w9c_UX3dd+7LdWNXCEwjnAG+bYWxqKYo_fzakWQu=Bg@mail.gmail.com>
<CALDj+BZE1KtMGpMH3UHtxjN2vXxu39o_hAWPdg==KLsWpe1zqA@mail.gmail.com>
<20140308085242.GA5727@odo.localdomain>
<CALDj+BYoYy8LWTgguj7FnrGMHuA5hgFdcFenBTdcxMuOwJ+tdA@mail.gmail.com>
<lfl3p6$na3$1@ger.gmane.org>
From: Alex Kotenko <alexykot@gmail.com>
Date: Mon, 10 Mar 2014 19:47:55 +0000
X-Google-Sender-Auth: mz5VEJgOtkb9-PAIAL0mLosz7bc
Message-ID: <CALDj+BZ1onYCfP6bZnBdTNtFiLWK_jVSbtcQ3t5rptV+M3CWBQ@mail.gmail.com>
To: Andreas Schildbach <andreas@schildbach.de>
Content-Type: multipart/alternative; boundary=047d7bdc9e02a063f504f445e3b1
X-Spam-Score: -0.3 (/)
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.3 HTML_FONT_FACE_BAD BODY: HTML font face is not a word
-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: 1WN6Bl-0003LS-7E
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Instant / contactless 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: Mon, 10 Mar 2014 19:48:42 -0000
--047d7bdc9e02a063f504f445e3b1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Ah, I see, so it's only payee who has to enable it, payer side is on by
default. Then fine, situation is better than I thought. We'll look at
implementing BIP70 asap.
Best regards,
Alex Kotenko
2014-03-10 19:28 GMT+00:00 Andreas Schildbach <andreas@schildbach.de>:
> On 03/10/2014 04:09 PM, Alex Kotenko wrote:
>
> > =E2=80=8BYes, =E2=80=8BI'm certain about that we need to switch to BIP7=
0 asap. As I said
> > earlier - support among the wallets is the biggest problem here really.
> > Only Andreas' Wallet supports it right now AFAIK, and even in there it'=
s
> > only as "LABS feature", so will be turned off for most of users.
>
> Just a small clarification here. Bitcoin Wallet supports the customer
> side of the protocol since 2011, without any "Labs enabling"! This means
> you've got an install base of half a million devices that you can
> interoperate with. Sure, a lot of users will have Bluetooth switched
> off. The UI flow to enable it while paying is pretty smooth though.
>
> The merchant side used to have the Labs enabling but this is gone since
> a few weeks.
>
>
>
>
> -------------------------------------------------------------------------=
-----
> 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
>
--047d7bdc9e02a063f504f445e3b1
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">Ah, I see, so it's only payee who has to e=
nable it, payer side is on by default. Then fine, situation is better than =
I thought. We'll look at implementing BIP70 asap.</div>
</div><div class=3D"gmail_extra"><br clear=3D"all"><div><div dir=3D"ltr"><s=
pan style=3D"color:rgb(0,51,0);font-family:'courier new',monospace"=
>Best regards,=C2=A0</span><div><div><div style=3D"text-align:left"><font c=
olor=3D"#003300" face=3D"'courier new', monospace" style=3D"text-al=
ign:-webkit-auto">Alex Kotenko</font></div>
</div></div></div></div>
<br><br><div class=3D"gmail_quote">2014-03-10 19:28 GMT+00:00 Andreas Schil=
dbach <span dir=3D"ltr"><<a href=3D"mailto:andreas@schildbach.de" target=
=3D"_blank">andreas@schildbach.de</a>></span>:<br><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">
<div class=3D"">On 03/10/2014 04:09 PM, Alex Kotenko wrote:<br>
<br>
> =E2=80=8BYes, =E2=80=8BI'm certain about that we need to switch to=
BIP70 asap. As I said<br>
> earlier - support among the wallets is the biggest problem here really=
.<br>
> Only Andreas' Wallet supports it right now AFAIK, and even in ther=
e it's<br>
> only as "LABS feature", so will be turned off for most of us=
ers.<br>
<br>
</div>Just a small clarification here. Bitcoin Wallet supports the customer=
<br>
side of the protocol since 2011, without any "Labs enabling"! Thi=
s means<br>
you've got an install base of half a million devices that you can<br>
interoperate with. Sure, a lot of users will have Bluetooth switched<br>
off. The UI flow to enable it while paying is pretty smooth though.<br>
<br>
The merchant side used to have the Labs enabling but this is gone since<br>
a few weeks.<br>
<div class=3D"im HOEnZb"><br>
<br>
<br>
---------------------------------------------------------------------------=
---<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>
</div><div class=3D"HOEnZb"><div class=3D"h5">_____________________________=
__________________<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>
--047d7bdc9e02a063f504f445e3b1--
|
