Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.181 as permitted sender)
	client-ip=209.85.212.181; envelope-from=gavinandresen@gmail.com;
	helo=mail-wi0-f181.google.com; 
MIME-Version: 1.0
In-Reply-To: <CANEZrP33bRx6abbXcf6nQYiPXFOOWSsZJqiFZY+A08x6O3X+pg@mail.gmail.com>
References: <CANEZrP1gDxcKO8z4hgM9BJU6-+Ft0oaiCZjqjN4MxGEJCgs5Ng@mail.gmail.com>
	<CADu7o8MXuUVrRP0vsvEkPLJ4f=2pC6V7W3hYE0jCVDRKmvqu8A@mail.gmail.com>
	<CANEZrP33bRx6abbXcf6nQYiPXFOOWSsZJqiFZY+A08x6O3X+pg@mail.gmail.com>
Date: Fri, 13 Dec 2013 10:20:50 +1000
Message-ID: <CABsx9T0VEu15KXH_XPn+cAERQFz=Tmjqna6ZoNpLrxkzeKw9kQ@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=bcaec54fb5343a444804ed5f6ffb
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

--bcaec54fb5343a444804ed5f6ffb
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Dec 13, 2013 at 4:24 AM, Mike Hearn <mike@plan99.net> wrote:

> I think the right way to integrate BIP32 and BIP70 would be to specify
> output scripts as normal for backwards compatibility, and then allow each
> output to have an additional xpubkey and iteration count field. The
> iteration counts could be unsigned.
>

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

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.

(either saving state, so it knows it used xpubkey+10 last month and should
use xpubkey+11 this month, or maybe it knows I'm paid monthly and just uses
xpubkey+(number_of_months_from_date_in_original_payment_request).

-- 
--
Gavin Andresen

--bcaec54fb5343a444804ed5f6ffb
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Dec 13, 2013 at 4:24 AM, Mike Hearn <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:mike@plan99.net" target=3D"_blank">mike@plan99.net</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr">I think the right way to integrate BIP32 and BIP70 would b=
e to specify output scripts as normal for backwards compatibility, and then=
 allow each output to have an additional xpubkey and iteration count field.=
 The iteration counts could be unsigned.</div>
</blockquote><div><br></div><div>Why would there be an iteration count? The=
 payer would handle that, wouldn&#39;t they?</div><div><br></div><div>If th=
e use case is: =A0I give the Foundation a &quot;here&#39;s where to pay my =
salary&quot; PaymentRequest, maybe with several Outputs each having a diffe=
rent xpubkey, then it seems to me the Foundation&#39;s wallet software shou=
ld take care of iterating.</div>
<div><br></div><div>(either saving state, so it knows it used xpubkey+10 la=
st month and should use xpubkey+11 this month, or maybe it knows I&#39;m pa=
id monthly and just uses xpubkey+(number_of_months_from_date_in_original_pa=
yment_request).=A0</div>
</div><div><br></div>-- <br>--<br>Gavin Andresen<br>
</div></div>

--bcaec54fb5343a444804ed5f6ffb--