From: Tamas Blummer <tamas@bitsofproof•com>
To: Eric Lombrozo <elombrozo@gmail•com>,
Eric Lombrozo via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Dynamic Hierarchical Deterministic Key Trees
Date: Tue, 17 Nov 2015 14:10:17 +0100 [thread overview]
Message-ID: <9F747105-0BE5-48B0-9032-A0B4CBFC8A66@bitsofproof.com> (raw)
In-Reply-To: <em58ec03b8-7af4-4643-9414-679acc07fcba@platinum>
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
next prev parent reply other threads:[~2015-11-17 13:26 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 [this message]
2015-11-21 8:45 ` Eric Lombrozo
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=9F747105-0BE5-48B0-9032-A0B4CBFC8A66@bitsofproof.com \
--to=tamas@bitsofproof$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=elombrozo@gmail$(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