From: "Eric Lombrozo" <elombrozo@gmail•com>
To: "Tamas Blummer" <tamas@bitsofproof•com>,
"Eric Lombrozo via bitcoin-dev"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Dynamic Hierarchical Deterministic Key Trees
Date: Sat, 21 Nov 2015 08:45:10 +0000 [thread overview]
Message-ID: <em5e7d40c8-cabe-487e-a6ad-dfa73bbb4867@platinum> (raw)
In-Reply-To: <9F747105-0BE5-48B0-9032-A0B4CBFC8A66@bitsofproof.com>
Tamas,
You could use a key for both signing and for derivation of a deeper
level (and perhaps there are some applications for this, if you think of
any please let me know), but the use cases being considered involve
generation of signing key sequences from seeds that are easy to backup
and easy to share with others to simplify multidevice synchronization,
key management, account structures, etc... while also allowing for
privacy by making it nontrivial to associate transactions for an account
without knowing the seed/chain code.
As such, we generally refer to such sequences by a path to the immediate
parent node in the tree and reserve the children themselves for the
signing keys.
- Eric
------ Original Message ------
From: "Tamas Blummer" <tamas@bitsofproof•com>
To: "Eric Lombrozo" <elombrozo@gmail•com>; "Eric Lombrozo via
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
>use of a key both for signing and for derivation of a deeper level of
>the hierarchy ?
>
>Tamas Blummer
>
>> On Nov 17, 2015, at 12:40, Eric Lombrozo via bitcoin-dev
>><bitcoin-dev@lists•linuxfoundation.org> wrote:
>>
>> I've submitted a BIP proposal that solves the issue of needing to
>>predefine HD wallet structures and not being able to arbitrarily nest
>>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
>
prev parent reply other threads:[~2015-11-21 8:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 11:40 Eric Lombrozo
2015-11-17 13:10 ` Tamas Blummer
2015-11-21 8:45 ` Eric Lombrozo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=em5e7d40c8-cabe-487e-a6ad-dfa73bbb4867@platinum \
--to=elombrozo@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=tamas@bitsofproof$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox