From: Gavin Andresen <gavinandresen@gmail.com>
To: Mike Hearn <mike@plan99.net>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
Paul Rabahy <prabahy@gmail.com>
Subject: Re: [Bitcoin-development] Merge avoidance and P2P connection encryption
Date: Fri, 13 Dec 2013 10:20:50 +1000 [thread overview]
Message-ID: <CABsx9T0VEu15KXH_XPn+cAERQFz=Tmjqna6ZoNpLrxkzeKw9kQ@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP33bRx6abbXcf6nQYiPXFOOWSsZJqiFZY+A08x6O3X+pg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 892 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1318 bytes --]
next prev parent reply other threads:[~2013-12-13 0:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 16:03 [Bitcoin-development] Merge avoidance and P2P connection encryption Mike Hearn
2013-12-12 17:28 ` Paul Rabahy
2013-12-12 18:24 ` Mike Hearn
2013-12-13 0:20 ` Gavin Andresen [this message]
2013-12-13 0:26 ` Jeff Garzik
2013-12-13 14:43 ` Peter Todd
2013-12-13 17:26 ` Mike Hearn
2013-12-13 19:19 ` Mark Friedenbach
2013-12-13 21:49 ` Mike Hearn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABsx9T0VEu15KXH_XPn+cAERQFz=Tmjqna6ZoNpLrxkzeKw9kQ@mail.gmail.com' \
--to=gavinandresen@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=mike@plan99.net \
--cc=prabahy@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox