From: Jeff Garzik <jgarzik@bitpay•com>
To: Stephane Brossier <stephane@kill-bill•org>
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
Date: Mon, 27 Jan 2014 23:29:55 -0500 [thread overview]
Message-ID: <CAJHLa0P-Pu_hhaeogAH4QmOkypFWgvJkGADUwDvzoXwndvyTOg@mail.gmail.com> (raw)
In-Reply-To: <E1FDB3F2-25ED-4B99-979E-12CE943CBD66@kill-bill.org>
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.
Note: This is ONE
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
next prev parent reply other threads:[~2014-01-28 4:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 2:36 Stephane Brossier
2014-01-28 3:58 ` Kevin Greene
2014-01-28 4:29 ` Jeff Garzik [this message]
2014-01-28 4:43 ` Jeff Garzik
2014-01-28 5:07 ` PikaPay
2014-01-28 6:08 ` Odinn Cyberguerrilla
2014-01-28 6:48 ` Jeff Garzik
2014-01-28 6:34 ` Mike Hearn
2014-01-29 2:47 ` Stephane Brossier
2014-01-31 18:13 ` Mike Hearn
2014-02-08 2:57 ` Stephane Brossier
2014-02-09 2:48 ` Stephane Brossier
2014-02-11 10:00 ` Kevin Greene
2014-02-11 18:01 ` Stephane Brossier
2014-02-12 6:32 ` Kevin Greene
2014-02-12 6:37 ` Kevin Greene
2014-02-14 20:28 ` Stephane Brossier
2014-02-24 18:04 ` Stephane Brossier
2014-02-25 16:29 ` Mike Hearn
2014-02-25 18:40 ` Drak
2014-02-25 19:03 ` Jeremy Spilman
2014-02-25 19:06 ` Christophe Biocca
2014-02-26 3:53 ` Stephane Brossier
2014-02-26 10:30 ` Mike Hearn
2014-02-11 16:24 ` Mike Hearn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJHLa0P-Pu_hhaeogAH4QmOkypFWgvJkGADUwDvzoXwndvyTOg@mail.gmail.com \
--to=jgarzik@bitpay$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=pierre@kill-bill$(echo .)org \
--cc=stephane@kill-bill$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox