From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WTXQb-00019W-Oq for bitcoin-development@lists.sourceforge.net; Fri, 28 Mar 2014 14:06:37 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.45 as permitted sender) client-ip=209.85.219.45; envelope-from=mh.in.england@gmail.com; helo=mail-oa0-f45.google.com; Received: from mail-oa0-f45.google.com ([209.85.219.45]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WTXQb-0006Qv-09 for bitcoin-development@lists.sourceforge.net; Fri, 28 Mar 2014 14:06:37 +0000 Received: by mail-oa0-f45.google.com with SMTP id eb12so6116855oac.4 for ; Fri, 28 Mar 2014 07:06:31 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.182.219.167 with SMTP id pp7mr213578obc.85.1396015591643; Fri, 28 Mar 2014 07:06:31 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.71.231 with HTTP; Fri, 28 Mar 2014 07:06:31 -0700 (PDT) In-Reply-To: References: <612FFAAD-14FF-4261-927D-BD2E0F287257@bitsofproof.com> Date: Fri, 28 Mar 2014 15:06:31 +0100 X-Google-Sender-Auth: pjEA-4txKgREvN8Nhf5ELXOM8t4 Message-ID: From: Mike Hearn To: Gavin Andresen Content-Type: multipart/alternative; boundary=089e0141ab8270e0ef04f5ab35f9 X-Spam-Score: -0.5 (/) 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 (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 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: 1WTXQb-0006Qv-09 Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] BIP 70 refund field 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: Fri, 28 Mar 2014 14:06:38 -0000 --089e0141ab8270e0ef04f5ab35f9 Content-Type: text/plain; charset=UTF-8 Yeah. Though there's actually a proposal for recurring payments from the KillBill folks. I keep bugging BitPay to review it but it seems they're lagging behind there, so perhaps we should just move ahead with that candidate extension. On Fri, Mar 28, 2014 at 3:01 PM, Gavin Andresen wrote: > On Fri, Mar 28, 2014 at 9:18 AM, Tamas Blummer wrote: > >> May I ask how the current payment protocol is supposed to handle salaries? >> > > It doesn't. > > "walk before you run" and all that; lets see what problems we run into > with the minimal payment protocol we have now (like refund outputs you have > to remember forever) before we create an insurmountable set of problems by > trying to solve everything we can think of all at once. > > -- > -- > Gavin Andresen > --089e0141ab8270e0ef04f5ab35f9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Yeah. Though there's actually a proposal for recurring= payments from the KillBill folks. I keep bugging BitPay to review it but i= t seems they're lagging behind there, so perhaps we should just move ah= ead with that candidate extension.


On Fri, Mar 2= 8, 2014 at 3:01 PM, Gavin Andresen <gavinandresen@gmail.com><= /span> wrote:
=
On Fri, Mar 28, 2014 at 9:18 AM,= Tamas Blummer <tamas@bitsofproof.com> wrote:
May I as= k how the current payment protocol is supposed to handle salaries?

It doesn't.

"wa= lk before you run" and all that; lets see what problems we run into wi= th the minimal payment protocol we have now (like refund outputs you have t= o remember forever) before we create an insurmountable set of problems by t= rying to solve everything we can think of all at once.
--
--
Gavin Andresen

--089e0141ab8270e0ef04f5ab35f9--