public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Christopher Allen <ChristopherA@lifewithalacrity.com>
To: Adam Back <adam.back@gmail.com>,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>,
	adam@cypherspace.org
Cc: "Peter D. Gray" <peter@coinkite.com>
Subject: Re: [bitcoin-dev] Deterministic Entropy From BIP32 Keychains
Date: Mon, 6 Apr 2020 14:45:37 -0700	[thread overview]
Message-ID: <CACrqygCRn5FmSRp_240fRFcgqC+GfX2NOhT4V7teMtHwV6rdMg@mail.gmail.com> (raw)
In-Reply-To: <CALqxMTHUp34fJ=4auRCG1BwanU7SdsDRsjwXqyxpWXQh38CxoQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 660 bytes --]

Although I believe that there needs to be a review by a cryptographic
engineering expert (ideally Pieter Wuille, who may have to hold his nose to
give it a pragmatic review) and I believe such a review will likely some
suggest some improvements, I do think something in this area should be done.

For instance with the offline tool #LetheKit
https://github.com/BlockchainCommons/bc-lethe-kit, you could go to your
vault, input your BIP39 from an offline titanium key or SLIP39 Shamir
shards, and then derive a child key in BIP39 form that can be delivered via
QR from the air-gapped LetheKit to another device you take away.

— Christopher Allen

[-- Attachment #2: Type: text/html, Size: 840 bytes --]

  reply	other threads:[~2020-04-06 21:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06 17:36 [bitcoin-dev] Deterministic Entropy From BIP32 Keychains Rodolfo Novak
2020-04-06 20:02 ` Adam Back
2020-04-06 21:45   ` Christopher Allen [this message]
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=CACrqygCRn5FmSRp_240fRFcgqC+GfX2NOhT4V7teMtHwV6rdMg@mail.gmail.com \
    --to=christophera@lifewithalacrity.com \
    --cc=adam.back@gmail.com \
    --cc=adam@cypherspace.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=peter@coinkite.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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