public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99.net>
To: Chris Pacia <ctpacia@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] ECDH in the payment protocol
Date: Tue, 13 May 2014 12:29:43 +0200	[thread overview]
Message-ID: <CANEZrP2PMvxhBEAS+eoqJ+eWu-+9i9chj4ZogpJW34o7ghJEsw@mail.gmail.com> (raw)
In-Reply-To: <53714DCE.7020803@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 774 bytes --]

On Tue, May 13, 2014 at 12:40 AM, Chris Pacia <ctpacia@gmail.com> wrote:

> Just a thought. Using the payment protocol for stealth would mean we
> would likely have to return to backing up wallets all the time would it
> not?
>

I think you are right. Awkward.

Wallets could auto-respend transactions to a plain (private) HD derived key
to make them findable again. But that gets us back to using block space
inefficiently.

Over time I think wallet backups will get more valuable anyway, as they
will start containing more and more essential data that isn't in the block
chain: receipts, messages, exchange rate records for tax purposes etc. But
being able to get access to your money with just the 12 words (+a date for
SPV wallets) is a pretty desirable safety feature.

[-- Attachment #2: Type: text/html, Size: 1142 bytes --]

  reply	other threads:[~2014-05-13 10:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09 12:05 [Bitcoin-development] ECDH in the payment protocol Mike Hearn
2014-05-09 15:03 ` Peter Todd
2014-05-09 15:15   ` Mike Hearn
2014-05-09 15:27     ` Peter Todd
2014-05-09 15:34       ` Mike Hearn
2014-05-09 15:43         ` Peter Todd
2014-05-09 16:12           ` Mike Hearn
2014-05-09 15:50         ` Pieter Wuille
2014-05-09 18:13           ` Peter Todd
2014-05-09 18:38             ` Pieter Wuille
2014-05-12 13:07               ` Peter Todd
2014-05-12 22:40               ` Chris Pacia
2014-05-13 10:29                 ` Mike Hearn [this message]
2014-05-13  9:19   ` Jeff Garzik

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=CANEZrP2PMvxhBEAS+eoqJ+eWu-+9i9chj4ZogpJW34o7ghJEsw@mail.gmail.com \
    --to=mike@plan99.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=ctpacia@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