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-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XqLae-0004fa-I4 for bitcoin-development@lists.sourceforge.net; Mon, 17 Nov 2014 12:39:32 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.173 as permitted sender) client-ip=209.85.213.173; envelope-from=pieter.wuille@gmail.com; helo=mail-ig0-f173.google.com; Received: from mail-ig0-f173.google.com ([209.85.213.173]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XqLad-0003lE-NX for bitcoin-development@lists.sourceforge.net; Mon, 17 Nov 2014 12:39:32 +0000 Received: by mail-ig0-f173.google.com with SMTP id r2so1219009igi.12 for ; Mon, 17 Nov 2014 04:39:26 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.50.138.76 with SMTP id qo12mr25572408igb.43.1416227966370; Mon, 17 Nov 2014 04:39:26 -0800 (PST) Received: by 10.50.248.5 with HTTP; Mon, 17 Nov 2014 04:39:26 -0800 (PST) In-Reply-To: <5469EAA5.1020606@gmail.com> References: <201411161724.19573.luke@dashjr.org> <5469692F.9030702@gmail.com> <5469EAA5.1020606@gmail.com> Date: Mon, 17 Nov 2014 13:39:26 +0100 Message-ID: From: Pieter Wuille To: Chris Pacia Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.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 (pieter.wuille[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -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: 1XqLad-0003lE-NX Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Increasing the OP_RETURN maximum payload size 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: Mon, 17 Nov 2014 12:39:32 -0000 On Mon, Nov 17, 2014 at 1:31 PM, Chris Pacia wrote: > If users wishes to use stealth addresses with out of band communication, the > benefits of HD would largely be lost and they would be back to making > regular backups -- this time after every transaction rather than every 100. That is inevitable for any wallet that offers any functionality beyond just maintaining a balance and the ability to send coins. In particular, anything that wishes to list previous transaction (with timestamps, history, metadata, messages sent using the payment protocol, ...) needs backups. What HD wallets (or any type of deterministic derivation scheme) offer is the fact that you can separate secret data and public data. You only need one safe backup of the master secret key - all the rest can at most result in privacy loss and not in lost coins. -- Pieter