Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1W80JG-0001sD-G2 for bitcoin-development@lists.sourceforge.net; Tue, 28 Jan 2014 04:30:02 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com designates 74.125.82.50 as permitted sender) client-ip=74.125.82.50; envelope-from=jgarzik@bitpay.com; helo=mail-wg0-f50.google.com; Received: from mail-wg0-f50.google.com ([74.125.82.50]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1W80JF-0001cT-Fq for bitcoin-development@lists.sourceforge.net; Tue, 28 Jan 2014 04:30:02 +0000 Received: by mail-wg0-f50.google.com with SMTP id l18so6905203wgh.5 for ; Mon, 27 Jan 2014 20:29:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=qAHitrZdwGuYpckVcw6AaBQY/6f5wbPMpGx2/Glcp7A=; b=KKem6HkdqOm95OlVgc0axnWxMchmy/zPOuVu/FEfkmZ//Pyx9C/x9n1bZRppv30UF0 Ns2TtttybKT9fLMtFTTfi3Z0GnYxGeLOiAyX4IVOYUr7pM0/l1xrequYDZq7r0bymoW4 iz6Yu+cyWVmn9huBosmcL5dVhDej6zfVB1ilp/MoNp+4FzIdZvZX5H05qikkyjQFlqUZ 5IN8ntkRNBL36yHK96/yzpOi/SO+uhDWExYMnl7uLymY7KYk/eARizS3yV03m0OMZFjK 61gkxgIgSdomoYCAV5x1BHr1ossbhxrNKQR68Lhp+A3CUzaRLpHRJBoqE9x/qCir/Sk2 cAUQ== X-Gm-Message-State: ALoCoQlzhxU1ZU7QHK1pGL6C9Np2oE0F1fqyx/unLR7m+40nYMqTNc1AdHWfC30867V0q6iVjibt MIME-Version: 1.0 X-Received: by 10.180.184.105 with SMTP id et9mr13908083wic.36.1390883395226; Mon, 27 Jan 2014 20:29:55 -0800 (PST) Received: by 10.194.2.164 with HTTP; Mon, 27 Jan 2014 20:29:55 -0800 (PST) In-Reply-To: References: Date: Mon, 27 Jan 2014 23:29:55 -0500 Message-ID: From: Jeff Garzik To: Stephane Brossier Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.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 SPF_PASS SPF: sender matches SPF record -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: 1W80JF-0001cT-Fq Cc: Bitcoin Dev , Pierre-Alexandre Meyer 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jan 2014 04:30:02 -0000 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/