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 1TfWTS-0002zm-2L for bitcoin-development@lists.sourceforge.net; Mon, 03 Dec 2012 13:54:18 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.175 as permitted sender) client-ip=209.85.214.175; envelope-from=pieter.wuille@gmail.com; helo=mail-ob0-f175.google.com; Received: from mail-ob0-f175.google.com ([209.85.214.175]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1TfWTR-0005n5-FZ for bitcoin-development@lists.sourceforge.net; Mon, 03 Dec 2012 13:54:18 +0000 Received: by mail-ob0-f175.google.com with SMTP id vb8so2545631obc.34 for ; Mon, 03 Dec 2012 05:54:12 -0800 (PST) MIME-Version: 1.0 Received: by 10.60.171.16 with SMTP id aq16mr8024363oec.37.1354542852169; Mon, 03 Dec 2012 05:54:12 -0800 (PST) Received: by 10.76.143.38 with HTTP; Mon, 3 Dec 2012 05:54:12 -0800 (PST) In-Reply-To: <1354542572.51243.YahooMailNeo@web121001.mail.ne1.yahoo.com> References: <1354542572.51243.YahooMailNeo@web121001.mail.ne1.yahoo.com> Date: Mon, 3 Dec 2012 14:54:12 +0100 Message-ID: From: Pieter Wuille To: Amir Taaki Content-Type: multipart/alternative; boundary=bcaec54d3ef08960bd04cff315d8 X-Spam-Score: -0.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 1.0 HTML_MESSAGE BODY: HTML included in message -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: 1TfWTR-0005n5-FZ Cc: "bitcoin-development@lists.sourceforge.net" Subject: Re: [Bitcoin-development] BIP 32 HD wallets, accounts should be labels not numbers 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, 03 Dec 2012 13:54:18 -0000 --bcaec54d3ef08960bd04cff315d8 Content-Type: text/plain; charset=ISO-8859-1 On Mon, Dec 3, 2012 at 2:49 PM, Amir Taaki wrote: > Can this be amended? I think it makes much more sense to allow people to > input labels not numbers at this level. > > General category names for different accounts is much more human than > numbers, and you can still use incrementing numbers if you prefer. > There is no way to iterate over all strings. The intention is that a wallet application can detect a new account that becomes in use (e.g. during disaster recovery), so the accounts get assigned incrementing numbers. I wouldn't mind adding the ability to do "non-standard derivations" using arbitrary strings, if this recoverability property is not desired. -- Pieter --bcaec54d3ef08960bd04cff315d8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Mon, Dec 3, 20= 12 at 2:49 PM, Amir Taaki <zgenjix@yahoo.com> wrote:
Can this be amended? I think it makes much more sense to allow people to in= put labels not numbers at this level.

General category names for different accounts is much more human than numbe= rs, and you can still use incrementing numbers if you prefer.

There is no way to iterate over all strings. The int= ention is that a wallet application can detect a new account that becomes i= n use (e.g. during disaster recovery), so the accounts get assigned increme= nting numbers.

I wouldn't mind adding the ability to do "non-= standard derivations" using arbitrary strings, if this recoverability = property is not desired.

--=A0
Pieter

--bcaec54d3ef08960bd04cff315d8--