From: Ali Sherief <ali@notatether.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Encrypted (like BIP38) master private key
Date: Tue, 30 May 2023 10:08:02 +0000 [thread overview]
Message-ID: <gfD-2LnzCr5aG-DkxduQwI6Qd5zdMMA3quHucZ5g29CJEU6gHu8QSXeHkmtqYcLCdM6iV6HNyxzEduIAz2khQXCpOPQ65wgWr4sphpYGruQ=@notatether.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 815 bytes --]
Just like we have BIPP38 encrypted keys for singular private keys, I was wondering if it would be possible to come up with a way to encrypt an extended private key using reversible encryption.
BIP38 was designed with physical coins in mind, and in particular covers the cases for lot and sequence numbers in detail.
There is a case to be made that in an encrypted extended private key, the lot and sequence numbers can be placed in the HD derivation path. In particular they can be derived like this: m/lot'/sequence' and both of them use hardened derivation.
The advantage would be that coinmakers would only have to generate one master private key during manufacturing instead of a ton of private keys.
But this is not a very convincing advantage so I'd like to hear what is other people's take on this.
-Ali
[-- Attachment #2: Type: text/html, Size: 1959 bytes --]
reply other threads:[~2023-05-30 10:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='gfD-2LnzCr5aG-DkxduQwI6Qd5zdMMA3quHucZ5g29CJEU6gHu8QSXeHkmtqYcLCdM6iV6HNyxzEduIAz2khQXCpOPQ65wgWr4sphpYGruQ=@notatether.com' \
--to=ali@notatether.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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