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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <kgreenek@gmail.com>) id 1W7zp1-0006Nk-U1
for bitcoin-development@lists.sourceforge.net;
Tue, 28 Jan 2014 03:58:47 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.44 as permitted sender)
client-ip=209.85.212.44; envelope-from=kgreenek@gmail.com;
helo=mail-vb0-f44.google.com;
Received: from mail-vb0-f44.google.com ([209.85.212.44])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1W7zp0-0008UK-Om
for bitcoin-development@lists.sourceforge.net;
Tue, 28 Jan 2014 03:58:47 +0000
Received: by mail-vb0-f44.google.com with SMTP id f12so3971761vbg.17
for <bitcoin-development@lists.sourceforge.net>;
Mon, 27 Jan 2014 19:58:41 -0800 (PST)
X-Received: by 10.52.111.38 with SMTP id if6mr572513vdb.12.1390881521208; Mon,
27 Jan 2014 19:58:41 -0800 (PST)
MIME-Version: 1.0
Received: by 10.58.86.9 with HTTP; Mon, 27 Jan 2014 19:58:21 -0800 (PST)
In-Reply-To: <E1FDB3F2-25ED-4B99-979E-12CE943CBD66@kill-bill.org>
References: <E1FDB3F2-25ED-4B99-979E-12CE943CBD66@kill-bill.org>
From: Kevin Greene <kgreenek@gmail.com>
Date: Mon, 27 Jan 2014 19:58:21 -0800
Message-ID: <CAEY8wq7zyE4JGBwQXjjxjfGMrgyPwfEeVVty5cw4sniFXVnEwg@mail.gmail.com>
To: Stephane Brossier <stephane@kill-bill.org>
Content-Type: multipart/alternative; boundary=bcaec548a041ff44e604f0ffd678
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
(kgreenek[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: 1W7zp0-0008UK-Om
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
Pierre-Alexandre Meyer <pierre@kill-bill.org>
Subject: Re: [Bitcoin-development] Extension for BIP-0070 to support
recurring 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: Tue, 28 Jan 2014 03:58:48 -0000
--bcaec548a041ff44e604f0ffd678
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
+1 to the idea of recurring payment requests.
Perhaps one way to realize this would be to add an optional URL to the
PaymentRequest object where the next PaymentRequest can be fetched and the
date at which the merchant expects the next payment.
On Mon, Jan 27, 2014 at 6:36 PM, Stephane Brossier
<stephane@kill-bill.org>wrote:
> Hi,
>
> [I sent this email 2 days ago prior my registration to the mailing list;
> please forgive me if this is a duplicate]
>
> I would like to propose an extension to the Payment Protocol (bip-0070) t=
o
> address the case of recurring payments in Bitcoin -- new bip or
> modification of bip-0070.
>
> There has been a lot of growth in the last few years in the 'subscription
> economy' with many new companies embracing that model -- online video,
> gaming, groceries, newspapers,... In parallel, Bitcoin is growing into a
> mainstream currency (hence bip-0070), and so the next logical step would =
be
> to define a protocol to address that need.
>
> We have been working in the past few years on an open-source billing
> platform (http://kill-bill.org/), and recently came with a prototype to
> do recurring billing in Bitcoin (see
> http://thekillbillstory.wordpress.com/2014/01/20/bitcoin-plugin/ and
> http://thekillbillstory.wordpress.com/2014/01/11/coinbase-integration-exp=
eriment/
> ).
>
>
> The work flow would look similar to the one from bip-0070. There would
> need to be some additions; the flow could be summarized as follow:
>
> 0. Click: 'Subscribe Now'
> 1. Wallet would get a RecurringPaymentRequestAuth which describes the
> nature of the future recurring payments
> 2. The Customer would get prompted from the wallet to authorize it.
> 3. The wallet would then poll the Merchant server (startup time, and/or
> well defined frequency) and potentially merchant would start issuing a
> PaymentRequest); the role of the wallet is to ensure that PaymentRequest =
is
> within the bounds of what was accepted by the customer-- amount,
> frequency,.. If it is, then it would make the Payment the same way it wor=
ks
> for bip-0070
>
> Is that something that the community would be interested in? We could
> provide more details about the protocol we have in mind (messages and
> flow), and also provide an implementation with bitcoinj as a wallet and
> Kill Bill as a merchant server.
>
> Le me know what you think.
>
> St=E9phane
>
>
> -------------------------------------------------------------------------=
-----
> 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=3D123612991&iu=3D/4140/ostg=
.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--bcaec548a041ff44e604f0ffd678
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"color:#336666">+1 to=
the idea of recurring payment requests.</div><div class=3D"gmail_default" =
style=3D"color:#336666"><br></div><div class=3D"gmail_default" style=3D"col=
or:#336666">
Perhaps one way to realize this would be to add an optional URL to the Paym=
entRequest object where the next PaymentRequest can be fetched and the date=
at which the merchant expects the next payment.</div></div><div class=3D"g=
mail_extra">
<br><br><div class=3D"gmail_quote">On Mon, Jan 27, 2014 at 6:36 PM, Stephan=
e Brossier <span dir=3D"ltr"><<a href=3D"mailto:stephane@kill-bill.org" =
target=3D"_blank">stephane@kill-bill.org</a>></span> wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">
<div style=3D"word-wrap:break-word"><div>Hi,</div><div><div><br></div><div>=
[I sent this email 2 days ago prior my registration to the mailing list; pl=
ease forgive me if this is a duplicate]</div><div><br></div><div>I would li=
ke to propose an extension to the Payment Protocol (bip-0070) to address th=
e case of recurring payments in Bitcoin -- new bip or modification of=A0bip=
-0070.</div>
<div><br></div><div>There has been a lot of growth in the last few years in=
the 'subscription economy' with many new companies embracing that =
model -- online video, gaming, groceries, newspapers,... In parallel, Bitco=
in is growing into a mainstream currency (hence=A0bip-0070), and so the nex=
t logical step would be to define a protocol to address that need.</div>
<div><br></div><div>We have been working in the past few years on an open-s=
ource billing platform (<a href=3D"http://kill-bill.org/" target=3D"_blank"=
>http://kill-bill.org/</a>), and recently came with a prototype to do recur=
ring billing in Bitcoin (see=A0<a href=3D"http://thekillbillstory.wordpress=
.com/2014/01/20/bitcoin-plugin/" target=3D"_blank">http://thekillbillstory.=
wordpress.com/2014/01/20/bitcoin-plugin/</a>=A0and=A0<a href=3D"http://thek=
illbillstory.wordpress.com/2014/01/11/coinbase-integration-experiment/" tar=
get=3D"_blank">http://thekillbillstory.wordpress.com/2014/01/11/coinbase-in=
tegration-experiment/</a>).</div>
<div><br></div><div><br></div><div>The work flow would look similar to the =
one from bip-0070. There would need to be some additions; the flow could be=
summarized as follow:</div><div><br></div><div>0. Click: 'Subscribe No=
w'</div>
<div>1. Wallet would get =A0a RecurringPaymentRequestAuth which describes t=
he nature of the future recurring payments</div><div>2. The Customer would =
get prompted from the wallet to authorize it.</div><div>3. The wallet would=
then poll the Merchant server (startup time, and/or well defined frequency=
) and potentially merchant would start issuing a PaymentRequest); the role =
of the wallet is to ensure that PaymentRequest is within the bounds of what=
was accepted by the customer-- amount, frequency,.. If it is, then it woul=
d make the Payment the same way it works for bip-0070</div>
<div><br></div><div>Is that something that the community would be intereste=
d in? We could provide more details about the protocol we have in mind (mes=
sages and flow), and also provide an implementation with bitcoinj as a wall=
et and Kill Bill as a merchant server.</div>
<div><br></div><div>Le me know what you think.</div><div><br></div><div>St=
=E9phane</div></div></div><br>---------------------------------------------=
---------------------------------<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. =A0Skip the complicated setup - simply import<b=
r>
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>__________________=
_____________________________<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>
<br></blockquote></div><br></div>
--bcaec548a041ff44e604f0ffd678--
|
