summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorOdinn Cyberguerrilla <odinn.cyberguerrilla@riseup.net>2014-01-27 22:08:43 -0800
committerbitcoindev <bitcoindev@gnusha.org>2014-01-28 06:08:50 +0000
commit484335433947de75b899bee92293988acfb597da (patch)
tree7ed5789efb88a614ec772df424df1b0a4350bab1
parent51347fb7f614f51083545b8539e230b31049d656 (diff)
downloadpi-bitcoindev-484335433947de75b899bee92293988acfb597da.tar.gz
pi-bitcoindev-484335433947de75b899bee92293988acfb597da.zip
Re: [Bitcoin-development] Extension for BIP-0070 to support recurring payments
-rw-r--r--1a/8c97ec28652258a802fd1d46fab5626c875cb6149
1 files changed, 149 insertions, 0 deletions
diff --git a/1a/8c97ec28652258a802fd1d46fab5626c875cb6 b/1a/8c97ec28652258a802fd1d46fab5626c875cb6
new file mode 100644
index 000000000..50b33ad9b
--- /dev/null
+++ b/1a/8c97ec28652258a802fd1d46fab5626c875cb6
@@ -0,0 +1,149 @@
+Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
+ helo=mx.sourceforge.net)
+ by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
+ (envelope-from <odinn.cyberguerrilla@riseup.net>) id 1W81qs-0005av-QJ
+ for bitcoin-development@lists.sourceforge.net;
+ Tue, 28 Jan 2014 06:08:50 +0000
+Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of riseup.net
+ designates 198.252.153.129 as permitted sender)
+ client-ip=198.252.153.129;
+ envelope-from=odinn.cyberguerrilla@riseup.net;
+ helo=mx1.riseup.net;
+Received: from mx1.riseup.net ([198.252.153.129])
+ by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
+ (Exim 4.76) id 1W81qr-0003bU-My
+ for bitcoin-development@lists.sourceforge.net;
+ Tue, 28 Jan 2014 06:08:50 +0000
+Received: from fulvetta.riseup.net (fulvetta-pn.riseup.net [10.0.1.75])
+ (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
+ (Client CN "*.riseup.net",
+ Issuer "Gandi Standard SSL CA" (not verified))
+ by mx1.riseup.net (Postfix) with ESMTPS id 956434EFF4;
+ Mon, 27 Jan 2014 22:08:43 -0800 (PST)
+Received: from [127.0.0.1] (localhost [127.0.0.1])
+ (Authenticated sender: odinn.cyberguerrilla@fulvetta.riseup.net)
+ with ESMTPSA id 2D558281
+Received: from localhost (127.0.0.1)
+ (SquirrelMail authenticated user odinn.cyberguerrilla)
+ by fulvetta.riseup.net with HTTP; Mon, 27 Jan 2014 22:08:43 -0800
+Message-ID: <ffaba6419d12b997feb1f421538d3b0b.squirrel@fulvetta.riseup.net>
+In-Reply-To: <CAJHLa0NvufgU6NUKWR6a_foibtEVGSmpMjTB2_pqFhqrEGMssw@mail.gmail.com>
+References: <E1FDB3F2-25ED-4B99-979E-12CE943CBD66@kill-bill.org>
+ <CAJHLa0NvufgU6NUKWR6a_foibtEVGSmpMjTB2_pqFhqrEGMssw@mail.gmail.com>
+Date: Mon, 27 Jan 2014 22:08:43 -0800
+From: "Odinn Cyberguerrilla" <odinn.cyberguerrilla@riseup.net>
+To: "Jeff Garzik" <jgarzik@bitpay.com>
+User-Agent: SquirrelMail/1.4.21
+MIME-Version: 1.0
+Content-Type: text/plain;charset=utf-8
+X-Priority: 3 (Normal)
+Importance: Normal
+X-Virus-Scanned: clamav-milter 0.97.8 at mx1
+X-Virus-Status: Clean
+Content-Transfer-Encoding: quoted-printable
+X-Spam-Score: -2.0 (--)
+X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
+ See http://spamassassin.org/tag/ for more details.
+ -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
+ no trust [198.252.153.129 listed in list.dnswl.org]
+ -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
+ sender-domain
+ -0.0 SPF_HELO_PASS SPF: HELO matches SPF record
+ -0.0 SPF_PASS SPF: sender matches SPF record
+ -0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay
+ domain
+ 0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay
+ lines
+X-Headers-End: 1W81qr-0003bU-My
+Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
+ Stephane Brossier <stephane@kill-bill.org>,
+ 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 06:08:50 -0000
+
+Greatly appreciate seeing this discussion occur. This is something that
+potentially could be supported through a bounty - possibly a process BIP?
+
+Possibly related: https://gist.github.com/ABISprotocol/8515891
+
+> 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, s=
+o
+> we
+> have a "push" model for payment, and the user has complete control. Th=
+e
+> 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 bo=
+ts
+> 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 a=
+nd
+> 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 revi=
+ew
+> into the process, with all that entails.
+>
+> --
+> Jeff Garzik
+> Bitcoin core developer and open source evangelist
+> BitPay, Inc. https://bitpay.com/
+> -----------------------------------------------------------------------=
+-------
+> 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/os=
+tg.clktrk_______________________________________________
+> Bitcoin-development mailing list
+> Bitcoin-development@lists.sourceforge.net
+> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
+>
+
+
+
+