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-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VrGUz-0002B3-Vg for bitcoin-development@lists.sourceforge.net; Fri, 13 Dec 2013 00:20:58 +0000 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; Received: from mail-wi0-f181.google.com ([209.85.212.181]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VrGUz-000897-4O for bitcoin-development@lists.sourceforge.net; Fri, 13 Dec 2013 00:20:57 +0000 Received: by mail-wi0-f181.google.com with SMTP id hq4so374660wib.8 for ; Thu, 12 Dec 2013 16:20:50 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.180.74.174 with SMTP id u14mr459209wiv.45.1386894050606; Thu, 12 Dec 2013 16:20:50 -0800 (PST) Received: by 10.195.13.68 with HTTP; Thu, 12 Dec 2013 16:20:50 -0800 (PST) In-Reply-To: References: Date: Fri, 13 Dec 2013 10:20:50 +1000 Message-ID: From: Gavin Andresen To: Mike Hearn Content-Type: multipart/alternative; boundary=bcaec54fb5343a444804ed5f6ffb X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gavinandresen[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: plan99.net] 1.0 HTML_MESSAGE BODY: HTML included in message -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: 1VrGUz-000897-4O Cc: Bitcoin Dev , Paul Rabahy Subject: Re: [Bitcoin-development] Merge avoidance and P2P connection encryption 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, 13 Dec 2013 00:20:58 -0000 --bcaec54fb5343a444804ed5f6ffb Content-Type: text/plain; charset=ISO-8859-1 On Fri, Dec 13, 2013 at 4:24 AM, Mike Hearn 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
On F= ri, Dec 13, 2013 at 4:24 AM, Mike Hearn <mike@plan99.net> wrot= e:
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.

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

If th= e use case is: =A0I give the Foundation a "here's where to pay my = salary" PaymentRequest, maybe with several Outputs each having a diffe= rent xpubkey, then it seems to me the Foundation's wallet software shou= ld take care of iterating.

(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'm pa= id monthly and just uses xpubkey+(number_of_months_from_date_in_original_pa= yment_request).=A0

--
--
Gavin Andresen
--bcaec54fb5343a444804ed5f6ffb--