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; 
MIME-Version: 1.0
Sender: mh.in.england@gmail.com
In-Reply-To: <CABsx9T1POJ3KTqSz_c=SdYTg=EKWa9jqjOpHPZoMoPGXozsvJA@mail.gmail.com>
References: <CANEZrP0AwR3WgHfwYWcrC9Z_MHPDwymWXAQwp7D8XZ+o2FsK8g@mail.gmail.com>
	<612FFAAD-14FF-4261-927D-BD2E0F287257@bitsofproof.com>
	<D7D06593-1987-490A-8DCD-21922E022E39@bitsofproof.com>
	<CABsx9T1POJ3KTqSz_c=SdYTg=EKWa9jqjOpHPZoMoPGXozsvJA@mail.gmail.com>
Date: Fri, 28 Mar 2014 15:06:31 +0100
Message-ID: <CANEZrP3BzGBcAgeppqbyYX4CcAH2ZVn+_-YUdCJRgSzBagOCpA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: multipart/alternative; boundary=089e0141ab8270e0ef04f5ab35f9
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP 70 refund field
Precedence: list

--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 <gavinandresen@gmail.com>wrote:

> On Fri, Mar 28, 2014 at 9:18 AM, Tamas Blummer <tamas@bitsofproof.com>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

<div dir=3D"ltr">Yeah. Though there&#39;s actually a proposal for recurring=
 payments from the KillBill folks. I keep bugging BitPay to review it but i=
t seems they&#39;re lagging behind there, so perhaps we should just move ah=
ead with that candidate extension.</div>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri, Mar 2=
8, 2014 at 3:01 PM, Gavin Andresen <span dir=3D"ltr">&lt;<a href=3D"mailto:=
gavinandresen@gmail.com" target=3D"_blank">gavinandresen@gmail.com</a>&gt;<=
/span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra">=
<div class=3D"gmail_quote"><div class=3D"">On Fri, Mar 28, 2014 at 9:18 AM,=
 Tamas Blummer <span dir=3D"ltr">&lt;<a href=3D"mailto:tamas@bitsofproof.co=
m" target=3D"_blank">tamas@bitsofproof.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word">May I as=
k how the current payment protocol is supposed to handle salaries?</div></b=
lockquote>

<div><br></div></div><div>It doesn&#39;t.</div><div><br></div><div>&quot;wa=
lk before you run&quot; 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.</div>
<span class=3D"HOEnZb"><font color=3D"#888888">
</font></span></div><span class=3D"HOEnZb"><font color=3D"#888888"><div><br=
></div>-- <br>--<br>Gavin Andresen<br>
</font></span></div></div>
</blockquote></div><br></div>

--089e0141ab8270e0ef04f5ab35f9--