From: "'Russell O'Connor' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] BIP39 Extension for Manual Seed Phrase Creation
Date: Wed, 4 Jun 2025 13:45:04 -0400 [thread overview]
Message-ID: <CAMZUoKnzDf0hMC-i4Xis3GXW96fWRwJgKSzzcj5aqGg3zGM8Kg@mail.gmail.com> (raw)
In-Reply-To: <20250525214153.163D47C0BC6@smtp.postman.i2p>
[-- Attachment #1: Type: text/plain, Size: 1920 bytes --]
On Wed, Jun 4, 2025 at 3:57 AM pithosian <pithosian@i2pmail.org> wrote:
> I'm not totally against thinking about different ways to (effectively)
> represent the data you'd use a descriptor for for simple use-cases,
> just not personally convinced on the utility of a purely
> hand-calculated mnemonic given the requirement of running (off the top
> of my head) SHA512 PBKDF2 for the BIP 32 seed, and a SHA512 HMAC for
> going from that to the root priv.
>
IMHO, the difference is that it is at least possible to cross-check the
derivation of pubkeys and addresses from the master seed using hardware
from different vendors. However it isn't really possible to cross-check
the quality of the initial random generation. Some people are going to
prefer to generate that randomness by hand in a fully transparent process
and not hidden within some computer chip using a noisy transistor or
whatever.
Once again, I want to reiterate for this thread that there already exists a
BIP for a hand-computable friendly master secret format, which is BIP-93
(codex32). Yes, hand computing the checksum for BIP-93 is a pain, but
unlike BIP-39's checksum, it is actually doable. And unlike BIP-39's
checksum, the checksum for codex32 is actually an error-correcting code, so
you can actually repair errors and erasures in the data. It is even
possible to use an untrusted computer to repair your codex32 string so that
the computer learns practically zero information about your secret or
secret share.
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/CAMZUoKnzDf0hMC-i4Xis3GXW96fWRwJgKSzzcj5aqGg3zGM8Kg%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 2567 bytes --]
next prev parent reply other threads:[~2025-06-04 18:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250523131541.1521C7C0DB0@smtp.postman.i2p>
2025-05-24 20:56 ` [bitcoindev] BIP39 Extension for Manual Seed Phrase Creation pithosian
2025-05-25 14:26 ` nerdyrugbyguy
[not found] ` <20250525154052.28C0E7C1013@smtp.postman.i2p>
2025-05-25 21:41 ` pithosian
2025-06-04 15:26 ` eric
2025-06-04 17:45 ` 'Russell O'Connor' via Bitcoin Development Mailing List [this message]
2025-05-23 11:25 Eric Kvam
2025-05-23 14:29 ` Kyle Honeycutt
[not found] ` <09A940A2-122A-445E-82EA-1B4E32AC7E34@gmail.com>
2025-05-23 20:45 ` 'Russell O'Connor' via Bitcoin Development Mailing List
2025-05-24 12:33 ` Eric Kvam
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=CAMZUoKnzDf0hMC-i4Xis3GXW96fWRwJgKSzzcj5aqGg3zGM8Kg@mail.gmail.com \
--to=bitcoindev@googlegroups.com \
--cc=roconnor@blockstream.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