public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@bitpay.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
	Paul Rabahy <prabahy@gmail.com>
Subject: Re: [Bitcoin-development] Merge avoidance and P2P connection encryption
Date: Thu, 12 Dec 2013 19:26:34 -0500	[thread overview]
Message-ID: <CAJHLa0NUNpGWXv4WFhtkM0WXQMFmX98Tvp_O5p7aWqLXHf+H_A@mail.gmail.com> (raw)
In-Reply-To: <CABsx9T0VEu15KXH_XPn+cAERQFz=Tmjqna6ZoNpLrxkzeKw9kQ@mail.gmail.com>

On Thu, Dec 12, 2013 at 7:20 PM, Gavin Andresen <gavinandresen@gmail.com> wrote:
> 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.  This is a key address-non-reuse case we really need to
solve.  Miner payouts, BitPay salary payouts, etc. all use a
statically provided, manually changed address.

Rotating through multiple outputs is a stopgap -- but IMO a useful
one.  HD wallets will solve this in a better way, but existing randkey
systems will be around for a long time.

-- 
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc.      https://bitpay.com/



  reply	other threads:[~2013-12-13  0:26 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
2013-12-13  0:26       ` Jeff Garzik [this message]
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=CAJHLa0NUNpGWXv4WFhtkM0WXQMFmX98Tvp_O5p7aWqLXHf+H_A@mail.gmail.com \
    --to=jgarzik@bitpay.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=gavinandresen@gmail.com \
    --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