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
111
112
113
114
115
116
117
118
119
|
Return-Path: <elombrozo@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 59108486
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 21 Nov 2015 08:45:28 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-pa0-f41.google.com (mail-pa0-f41.google.com
[209.85.220.41])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 967B387
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 21 Nov 2015 08:45:27 +0000 (UTC)
Received: by pacej9 with SMTP id ej9so140050571pac.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 21 Nov 2015 00:45:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=from:to:subject:date:message-id:in-reply-to:reply-to:user-agent
:mime-version:content-type:content-transfer-encoding;
bh=4ScJMU9qWCvv9ZLog5K411MPnfolC0UPJFECzJToVHQ=;
b=mQlR0K/D+/a+Nq5FKx1mkrWqn1Z550nNyKa9r9l+h9+CrBMTDKmRdwcFMkHAPScxQz
GcoUJ1W6+Sms4Jd8BOtJmIclUQKDqAkvymJ7K93HD8SLPhpA1vjdU01XDnO4tHYtVSK1
oWOfr1RZRqJE5e9k/pzvgVL3gpk1p7cRGp1X1OvWiQf1LWiQM4z75oxTzarGM76TX48E
d6Qz6aOsjSXD7JNbEDkbZsN4LzpF6E6O7mVhcCSQ1ek7ES3uIrKKx4KaAt4tjG394NQ4
fUCw2X0JdnlW37tkTmBKNoRyObc3kzNr7dIWHjddSCN/5cYkjNa4P2LcyLr8Hzj4JXIq
MU4A==
X-Received: by 10.66.124.165 with SMTP id mj5mr23989282pab.97.1448095527339;
Sat, 21 Nov 2015 00:45:27 -0800 (PST)
Received: from [192.168.1.108] (cpe-76-167-237-202.san.res.rr.com.
[76.167.237.202]) by smtp.gmail.com with ESMTPSA id
a27sm2233279pfj.36.2015.11.21.00.45.26
(version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
Sat, 21 Nov 2015 00:45:26 -0800 (PST)
From: "Eric Lombrozo" <elombrozo@gmail.com>
To: "Tamas Blummer" <tamas@bitsofproof.com>, "Eric Lombrozo via bitcoin-dev"
<bitcoin-dev@lists.linuxfoundation.org>
Date: Sat, 21 Nov 2015 08:45:10 +0000
Message-Id: <em5e7d40c8-cabe-487e-a6ad-dfa73bbb4867@platinum>
In-Reply-To: <9F747105-0BE5-48B0-9032-A0B4CBFC8A66@bitsofproof.com>
Reply-To: "Eric Lombrozo" <elombrozo@gmail.com>
User-Agent: eM_Client/6.0.23181.0
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM,
RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Sat, 21 Nov 2015 09:07:37 +0000
Subject: Re: [bitcoin-dev] Dynamic Hierarchical Deterministic Key Trees
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Nov 2015 08:45:28 -0000
Tamas,
You could use a key for both signing and for derivation of a deeper=20
level (and perhaps there are some applications for this, if you think of=
=20
any please let me know), but the use cases being considered involve=20
generation of signing key sequences from seeds that are easy to backup=20
and easy to share with others to simplify multidevice synchronization,=20
key management, account structures, etc... while also allowing for=20
privacy by making it nontrivial to associate transactions for an account=
=20
without knowing the seed/chain code.
As such, we generally refer to such sequences by a path to the immediate=
=20
parent node in the tree and reserve the children themselves for the=20
signing keys.
- Eric
------ Original Message ------
From: "Tamas Blummer" <tamas@bitsofproof.com>
To: "Eric Lombrozo" <elombrozo@gmail.com>; "Eric Lombrozo via=20
bitcoin-dev" <bitcoin-dev@lists.linuxfoundation.org>
Sent: 11/17/2015 5:10:17 AM
Subject: Re: [bitcoin-dev] Dynamic Hierarchical Deterministic Key Trees
>Hi Eric,
>
>Would you please enumerate, or point to, arguments that discourage the=20
>use of a key both for signing and for derivation of a deeper level of=20
>the hierarchy ?
>
>Tamas Blummer
>
>> On Nov 17, 2015, at 12:40, Eric Lombrozo via bitcoin-dev=20
>><bitcoin-dev@lists.linuxfoundation.org> wrote:
>>
>> I've submitted a BIP proposal that solves the issue of needing to=20
>>predefine HD wallet structures and not being able to arbitrarily nest=20
>>deeper levels. Comments appreciated.
>>
>> https://github.com/bitcoin/bips/pull/242
>>
>>
>> - Eric
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
|
