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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1W8pCc-0006mu-N6
for bitcoin-development@lists.sourceforge.net;
Thu, 30 Jan 2014 10:50:34 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.48 as permitted sender)
client-ip=209.85.219.48; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f48.google.com;
Received: from mail-oa0-f48.google.com ([209.85.219.48])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1W8pCa-0002V2-HS
for bitcoin-development@lists.sourceforge.net;
Thu, 30 Jan 2014 10:50:34 +0000
Received: by mail-oa0-f48.google.com with SMTP id l6so3406567oag.21
for <bitcoin-development@lists.sourceforge.net>;
Thu, 30 Jan 2014 02:50:22 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.182.223.37 with SMTP id qr5mr10906136obc.41.1391079022647;
Thu, 30 Jan 2014 02:50:22 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.76.99.112 with HTTP; Thu, 30 Jan 2014 02:50:22 -0800 (PST)
In-Reply-To: <lcdaid$rd4$1@ger.gmane.org>
References: <lc5hmg$1jh$1@ger.gmane.org>
<lcdaid$rd4$1@ger.gmane.org>
Date: Thu, 30 Jan 2014 11:50:22 +0100
X-Google-Sender-Auth: 2SJjn0-iL7g-lK1QKaNVetF6DHQ
Message-ID: <CANEZrP1Soi3TsLmoea-kEmPKp2J-10R4_Y0dd_XQfm8L3kbd=g@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Andreas Schildbach <andreas@schildbach.de>
Content-Type: multipart/alternative; boundary=f46d0444ee69ffe07904f12dd210
X-Spam-Score: -0.5 (/)
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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1W8pCa-0002V2-HS
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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, 30 Jan 2014 10:50:34 -0000
--f46d0444ee69ffe07904f12dd210
Content-Type: text/plain; charset=UTF-8
Although it should be noted that these binaries don't yet do URI support so
you can't scan a bitcoin URI with r= in it and see the verified merchant
name, etc. I think Andreas plans to do the UI for that in the next update.
On Thu, Jan 30, 2014 at 11:46 AM, Andreas Schildbach
<andreas@schildbach.de>wrote:
> Just a small update. I merged the code to my bitcoinj-0.11 branch and
> put up binary .apk files for experimentation. Just make sure to tick
> "BIP70 for tap-to-pay/scan-to-pay" in the labs settings.
>
> Source:
> https://github.com/schildbach/bitcoin-wallet/commits/bitcoinj-0.11
>
> Binaries:
>
> https://github.com/schildbach/bitcoin-wallet/releases/tag/v3.30-bitcoinj0.11
>
>
> On 01/27/2014 12:59 PM, Andreas Schildbach wrote:
> > As promised I'd like to present my work done on leveraging the payment
> > protocol for face-to-face payments. The general assumption is that
> > individuals don't own X.509 certificates. Their devices may be only
> > badly connected to the internet or in some cases not at all. I've
> > implemented a prototype on a branch of Bitcoin Wallet. It is using
> > bitcoinj 0.11 (not released).
> >
> > https://github.com/schildbach/bitcoin-wallet/commits/payment-protocol
>
>
>
>
> ------------------------------------------------------------------------------
> WatchGuard Dimension instantly turns raw network data into actionable
> security intelligence. It gives you real-time visual feedback on key
> security issues and trends. Skip the complicated setup - simply import
> a virtual appliance and go from zero to informed in seconds.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--f46d0444ee69ffe07904f12dd210
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Although it should be noted that these binaries don't =
yet do URI support so you can't scan a bitcoin URI with r=3D in it and =
see the verified merchant name, etc. I think Andreas plans to do the UI for=
that in the next update.</div>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu, Jan 3=
0, 2014 at 11:46 AM, Andreas Schildbach <span dir=3D"ltr"><<a href=3D"ma=
ilto:andreas@schildbach.de" target=3D"_blank">andreas@schildbach.de</a>>=
</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Just a small update. I merged the code to my=
bitcoinj-0.11 branch and<br>
put up binary .apk files for experimentation. Just make sure to tick<br>
"BIP70 for tap-to-pay/scan-to-pay" in the labs settings.<br>
<br>
Source:<br>
<a href=3D"https://github.com/schildbach/bitcoin-wallet/commits/bitcoinj-0.=
11" target=3D"_blank">https://github.com/schildbach/bitcoin-wallet/commits/=
bitcoinj-0.11</a><br>
<br>
Binaries:<br>
<a href=3D"https://github.com/schildbach/bitcoin-wallet/releases/tag/v3.30-=
bitcoinj0.11" target=3D"_blank">https://github.com/schildbach/bitcoin-walle=
t/releases/tag/v3.30-bitcoinj0.11</a><br>
<div class=3D"im HOEnZb"><br>
<br>
On 01/27/2014 12:59 PM, Andreas Schildbach wrote:<br>
> As promised I'd like to present my work done on leveraging the pay=
ment<br>
> protocol for face-to-face payments. The general assumption is that<br>
> individuals don't own X.509 certificates. Their devices may be onl=
y<br>
> badly connected to the internet or in some cases not at all. I've<=
br>
> implemented a prototype on a branch of Bitcoin Wallet. It is using<br>
> bitcoinj 0.11 (not released).<br>
><br>
> <a href=3D"https://github.com/schildbach/bitcoin-wallet/commits/paymen=
t-protocol" target=3D"_blank">https://github.com/schildbach/bitcoin-wallet/=
commits/payment-protocol</a><br>
<br>
<br>
<br>
</div><div class=3D"im HOEnZb">--------------------------------------------=
----------------------------------<br>
WatchGuard Dimension instantly turns raw network data into actionable<br>
security intelligence. It gives you real-time visual feedback on key<br>
security issues and trends. =C2=A0Skip the complicated setup - simply impor=
t<br>
a virtual appliance and go from zero to informed in seconds.<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D123612991&iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D123612991&iu=3D/4140/ostg.clktrk</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>
--f46d0444ee69ffe07904f12dd210--
|
