From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wk9y1-0001QS-PJ for bitcoin-development@lists.sourceforge.net; Tue, 13 May 2014 10:29:49 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.180 as permitted sender) client-ip=209.85.214.180; envelope-from=mh.in.england@gmail.com; helo=mail-ob0-f180.google.com; Received: from mail-ob0-f180.google.com ([209.85.214.180]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wk9y0-0004e0-QN for bitcoin-development@lists.sourceforge.net; Tue, 13 May 2014 10:29:49 +0000 Received: by mail-ob0-f180.google.com with SMTP id va2so135822obc.11 for ; Tue, 13 May 2014 03:29:43 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.182.29.225 with SMTP id n1mr40860709obh.2.1399976983245; Tue, 13 May 2014 03:29:43 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.71.162 with HTTP; Tue, 13 May 2014 03:29:43 -0700 (PDT) In-Reply-To: <53714DCE.7020803@gmail.com> References: <20140509150325.GA30436@savin> <20140509152715.GA12421@savin> <20140509181353.GB27819@savin> <53714DCE.7020803@gmail.com> Date: Tue, 13 May 2014 12:29:43 +0200 X-Google-Sender-Auth: 535UIlqeofSNMdKOO-8r2rzT-p0 Message-ID: From: Mike Hearn To: Chris Pacia Content-Type: multipart/alternative; boundary=001a11c2da9cc7bc7104f9458ad4 X-Spam-Score: -0.5 (/) 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 (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 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: 1Wk9y0-0004e0-QN Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] ECDH in the payment protocol 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: Tue, 13 May 2014 10:29:49 -0000 --001a11c2da9cc7bc7104f9458ad4 Content-Type: text/plain; charset=UTF-8 On Tue, May 13, 2014 at 12:40 AM, Chris Pacia 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. --001a11c2da9cc7bc7104f9458ad4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On T= ue, May 13, 2014 at 12:40 AM, Chris Pacia <ctpacia@gmail.com> wrote:
Just a thought. Using the payment protocol f= or 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 (pri= vate) 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 is= n't in the block chain: receipts, messages, exchange rate records for t= ax purposes etc. But being able to get access to your money with just the 1= 2 words (+a date for SPV wallets) is a pretty desirable safety feature.
--001a11c2da9cc7bc7104f9458ad4--