From: Adam Back <adam.back@gmail•com>
To: Rodolfo Novak <rodolfo@coinkite•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Cc: "Peter D. Gray" <peter@coinkite•com>
Subject: Re: [bitcoin-dev] Deterministic Entropy From BIP32 Keychains
Date: Mon, 6 Apr 2020 22:02:00 +0200 [thread overview]
Message-ID: <CALqxMTHUp34fJ=4auRCG1BwanU7SdsDRsjwXqyxpWXQh38CxoQ@mail.gmail.com> (raw)
In-Reply-To: <20200406173617.GI3523@coinkite.com>
I looked at it and consider the crypto choices reasonable and reusing
existing bitcoin dependencies in library crypto building blocks
mostly.
For myself i think the use-case of having an offline seed manager that
can be backed up once, and support multiple wallets, including ones
created after the backup improves a practical and under-addressed
problem for many users and businesses.
The fact that the interface between an offline seed manager and a
hardware or software wallet can be a bip39 mnemonic seed is convenient
and an improvement over using custom derivation paths for practical
use given the complexity of custom paths and variable support for them
in wallets.
Adam
On Mon, 6 Apr 2020 at 20:43, Rodolfo Novak via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
>
> Hello,
>
> We are planning on implementing the [Deterministic Entropy From BIP32 Keychains](https://gist.github.com/ethankosakovsky/268c52f018b94bea29a6e809381c05d6) BIP on Coldcard.
>
> Is there a BIP number planned to be assigned and is there any review of this BIP yet?
>
> Regards,
>
>
> ℝ.
>
> Rodolfo Novak || Coinkite Inc. || GPG: B444CDDA
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
next prev parent reply other threads:[~2020-04-06 20:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 17:36 Rodolfo Novak
2020-04-06 20:02 ` Adam Back [this message]
2020-04-06 21:45 ` Christopher Allen
2020-04-11 0:09 ` Ethan Kosakovsky
2020-04-16 17:53 ` Ethan Kosakovsky
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='CALqxMTHUp34fJ=4auRCG1BwanU7SdsDRsjwXqyxpWXQh38CxoQ@mail.gmail.com' \
--to=adam.back@gmail$(echo .)com \
--cc=adam@cypherspace$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=peter@coinkite$(echo .)com \
--cc=rodolfo@coinkite$(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