1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
|
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 <pieter.wuille@gmail.com>) 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 <bitcoin-development@lists.sourceforge.net>;
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: <CAPg+sBgU=1Z1KaGXk0xY1mzEZKVRPd7T06X_zcTUd_d4JUsWtw@mail.gmail.com>
From: Pieter Wuille <pieter.wuille@gmail.com>
To: Amir Taaki <zgenjix@yahoo.com>
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"
<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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=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 <zgenjix@yahoo.com> 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
<br><div class=3D"gmail_extra"><div class=3D"gmail_quote">On Mon, Dec 3, 20=
12 at 2:49 PM, Amir Taaki <span dir=3D"ltr"><<a href=3D"mailto:zgenjix@y=
ahoo.com" target=3D"_blank">zgenjix@yahoo.com</a>></span> wrote:<br><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">
Can this be amended? I think it makes much more sense to allow people to in=
put labels not numbers at this level.<br>
<br>
General category names for different accounts is much more human than numbe=
rs, and you can still use incrementing numbers if you prefer.<br></blockquo=
te><div><br></div><div>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.</div>
<div><br></div><div>I wouldn't mind adding the ability to do "non-=
standard derivations" using arbitrary strings, if this recoverability =
property is not desired.</div><div><br></div><div>--=A0</div><div>Pieter</d=
iv>
<div><br></div></div></div>
--bcaec54d3ef08960bd04cff315d8--
|
