Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bitpay.com
	designates 74.125.82.43 as permitted sender)
	client-ip=74.125.82.43; envelope-from=jgarzik@bitpay.com;
	helo=mail-wg0-f43.google.com; 
MIME-Version: 1.0
In-Reply-To: <E1FDB3F2-25ED-4B99-979E-12CE943CBD66@kill-bill.org>
References: <E1FDB3F2-25ED-4B99-979E-12CE943CBD66@kill-bill.org>
Date: Mon, 27 Jan 2014 23:43:58 -0500
Message-ID: <CAJHLa0NvufgU6NUKWR6a_foibtEVGSmpMjTB2_pqFhqrEGMssw@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
To: Stephane Brossier <stephane@kill-bill.org>
Content-Type: multipart/alternative; boundary=089e016347f0f3811b04f1007876
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
Precedence: list

--089e016347f0f3811b04f1007876
Content-Type: text/plain; charset=ISO-8859-1

Yes, recurring payments and subscriptions is a frequently-requested
feature.  It needs a new BIP.  Here is an outline:

The situation is somewhat analogous to HTML5 local storage.  The remote
(merchant) wants to initiate a persistent behavior.  This is bitcoin, so we
have a "push" model for payment, and the user has complete control.  The
merchant can, at most, send a "subscription request."  The user is
responsible for making on-time payments after that point.

Centralized services like coinbase.com or blockchain.info will have an easy
time of it.  An automated program on their backend, sending payments as
needed, is easy and direct.

More inventive services might employ multisig transactions, generating and
signing one signature of a TX, then sending that TX to the human for
further signing and publishing.  A few competing vendors could offer bots
that provide this signing service.

Decentralized, standalone wallet clients will be somewhat troublesome.  We
can store a local subscription request, and send recurring payments...  if
the wallet app is running.  If not, the user will be missing payments, that
perhaps they intended to make (rent!).

Each of these solutions can be cancelled at any time by the user.  As such,
a courtesy "subscription cancelled" message sent to the merchant is
recommended.  User controls the usage of their money at all times, the way
things should be.

And finally, you do not want to make it /too easy/ to send money over and
over again.  From a human-interface perspective, a textual reminder to send
money might be preferred over actual recurring payment automation: reminder
email + manual spend inserts a bit of additional human thought and review
into the process, with all that entails.

-- 
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc.      https://bitpay.com/

--089e016347f0f3811b04f1007876
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div>Yes, recurring payments and subscriptions i=
s a frequently-requested feature. =A0It needs a new BIP. =A0Here is an outl=
ine:<br><br>The situation is somewhat analogous to HTML5 local storage. =A0=
The remote (merchant) wants to initiate a persistent behavior.=A0 This is b=
itcoin, so we have a &quot;push&quot; model for payment, and the user has c=
omplete control.=A0 The merchant can, at most, send a &quot;subscription re=
quest.&quot;=A0 The user is responsible for making on-time payments after t=
hat point.<br>
<br>Centralized services like <a href=3D"http://coinbase.com">coinbase.com<=
/a> or <a href=3D"http://blockchain.info">blockchain.info</a> will have an =
easy time of it.=A0 An automated program on their backend, sending payments=
 as needed, is easy and direct.<br>
<br></div>More inventive services might employ multisig transactions, gener=
ating and signing one signature of a TX, then sending that TX to the human =
for further signing and publishing.=A0 A few competing vendors could offer =
bots that provide this signing service.<br>
<br></div>Decentralized, standalone wallet clients will be somewhat trouble=
some.=A0 We can store a local subscription request, and send recurring paym=
ents...=A0 if the wallet app is running.=A0 If not, the user will be missin=
g payments, that perhaps they intended to make (rent!).<br>
<br></div><div>Each of these solutions can be cancelled at any time by the =
user.=A0 As such, a courtesy &quot;subscription cancelled&quot; message sen=
t to the merchant is recommended.=A0 User controls the usage of their money=
 at all times, the way things should be.<br>
</div><div><br></div>And finally, you do not want to make it /too easy/ to =
send money over and over again.=A0 From a human-interface perspective, a te=
xtual reminder to send money might be preferred over actual recurring payme=
nt automation: reminder email + manual spend inserts a bit of additional hu=
man thought and review into the process, with all that entails.<br>
<div><div><div><br>-- <br>Jeff Garzik<br>Bitcoin core developer and open so=
urce evangelist<br>BitPay, Inc. =A0 =A0 =A0<a href=3D"https://bitpay.com/">=
https://bitpay.com/</a><br></div></div></div></div>

--089e016347f0f3811b04f1007876--