Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.219.51 as permitted sender)
	client-ip=209.85.219.51; envelope-from=mh.in.england@gmail.com;
	helo=mail-oa0-f51.google.com; 
MIME-Version: 1.0
Sender: mh.in.england@gmail.com
In-Reply-To: <CABsx9T0VEu15KXH_XPn+cAERQFz=Tmjqna6ZoNpLrxkzeKw9kQ@mail.gmail.com>
References: <CANEZrP1gDxcKO8z4hgM9BJU6-+Ft0oaiCZjqjN4MxGEJCgs5Ng@mail.gmail.com>
	<CADu7o8MXuUVrRP0vsvEkPLJ4f=2pC6V7W3hYE0jCVDRKmvqu8A@mail.gmail.com>
	<CANEZrP33bRx6abbXcf6nQYiPXFOOWSsZJqiFZY+A08x6O3X+pg@mail.gmail.com>
	<CABsx9T0VEu15KXH_XPn+cAERQFz=Tmjqna6ZoNpLrxkzeKw9kQ@mail.gmail.com>
Date: Fri, 13 Dec 2013 09:26:59 -0800
Message-ID: <CANEZrP1ha6y-w1Cpq+7t1ogUwNmxSobEREY2tawp7bcFGRPKiw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: multipart/alternative; boundary=f46d04479f930cd03a04ed6dc5c1
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
	Paul Rabahy <prabahy@gmail.com>
Subject: Re: [Bitcoin-development] Merge avoidance and P2P connection
	encryption
Precedence: list

--f46d04479f930cd03a04ed6dc5c1
Content-Type: text/plain; charset=UTF-8

>
> Why would there be an iteration count? The payer would handle that,
> wouldn't they?
>

I'm thinking about a use case I hope will become common next year -
pastebin style hosting sites for payment requests. Like, if I as a regular
end user wish to use the payment protocol, I could just upload a (possibly
signed) payment request to:

payr.com/a62gahZ

or whatever, and then payr.com can take care of incrementing the iteration
count on each download of my file. That's why it's useful for it to be
unsigned.


> If the use case is:  I give the Foundation a "here's where to pay my
> salary" PaymentRequest, maybe with several Outputs each having a different
> xpubkey, then it seems to me the Foundation's wallet software should take
> care of iterating.
>

Absolutely. The two use cases can both be supported. You could give
iteration ranges, for instance, if you want to specify expiry in terms of
number of payments rather than time.

--f46d04479f930cd03a04ed6dc5c1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div=
 class=3D"gmail_quote">
<div class=3D"im"><span style=3D"color:rgb(34,34,34)">Why would there be an=
 iteration count? The payer would handle that, wouldn&#39;t they?</span></d=
iv></div></div></div></blockquote><div><br></div><div>I&#39;m thinking abou=
t a use case I hope will become common next year - pastebin style hosting s=
ites for payment requests. Like, if I as a regular end user wish to use the=
 payment protocol, I could just upload a (possibly signed) payment request =
to:</div>
<div><br></div><div><a href=3D"http://payr.com/a62gahZ">payr.com/a62gahZ</a=
></div><div><br></div><div>or whatever, and then <a href=3D"http://payr.com=
">payr.com</a> can take care of incrementing the iteration count on each do=
wnload of my file. That&#39;s why it&#39;s useful for it to be unsigned.</d=
iv>
<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=
=3D"gmail_extra"><div class=3D"gmail_quote"><div class=3D"im"><span style=
=3D"color:rgb(34,34,34)">If the use case is: =C2=A0I give the Foundation a =
&quot;here&#39;s where to pay my salary&quot; PaymentRequest, maybe with se=
veral Outputs each having a different xpubkey, then it seems to me the Foun=
dation&#39;s wallet software should take care of iterating.</span></div>
</div></div></div></blockquote><div><br></div><div>Absolutely. The two use =
cases can both be supported. You could give iteration ranges, for instance,=
 if you want to specify expiry in terms of number of payments rather than t=
ime.</div>
</div></div></div>

--f46d04479f930cd03a04ed6dc5c1--