From: Pavol Rusnak <stick@satoshilabs•com>
To: Leslie <0300dbdd1b@protonmail•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Introducing a version field to BIP39 mnemonic phrases
Date: Sat, 13 Jan 2024 11:31:35 -0500 [thread overview]
Message-ID: <CAF90Av=HqhdOfLpY1Pz8J2N7f_A+L_LDcni2Rx59Z5rNpsLksQ@mail.gmail.com> (raw)
In-Reply-To: <qasgf9QSlEKnsWipYSu7ABTqKQbqa7kHwSQl7yM8ihEO9Kivk9pMtnx9tsl6q1frnmCijbmr5w6TDMadip8PFd_6GoLGipbCSwymhlMBwU4=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 2160 bytes --]
On Sat, 13 Jan 2024 at 10:53, Leslie <0300dbdd1b@protonmail•com> wrote:
> Developments like aezeed[1] or Electrum V2[2] also demonstrate that the
> standard BIP39 entropy might not always suffice for specific applications,
> leading to alternative standards being developed.
> This reality underscores the need to consider ways to enhance the existing
> system to more effectively accommodate these evolving requirements.
>
It is a very unrealistic that any kind of seed standard with extra metadata
will cover all possible future usecases.
Therefore new standards will always keep emerging.
LND coming up with a new aezeed standard and not using Electrum v2 are good
example of this.
For LND, the documentation[1] tells you to convert the seed using a website
(not great) AND on top of that you also need to provide the derivation path
for the funds(!) because the aezeed version is not used to encode the
derivation path used.
Probably the LND folks also realized it is not feasible to regenerate the
seed (and bother user with the backup)
every time wallet starts to use the new address format.
On the other side, CLN is perfectly fine with using BIP39, making it very
easy to recover CLN funds in any BIP39 compatible wallet.
[1]
https://www.lightningnode.info/technicals/restorelndonchainfundsinelectrum
In summary, while I hold deep respect for the fundamental principles of
> BIP39, I firmly believe that exploring the potential of versioned mnemonics
> can effectively address the dynamic nature of user practices and
> application demands, all while preserving the core strengths of the BIP39
> standard.
>
From where I stand, adding metadata to seed is a fool's errand.
Every year, new people coming to Bitcoin try it and fail.
Everything said, feel free to experiment, but your experiments should be
different standard than BIP39.
I would like to keep the BIP39 base entropy layer "ossified".
Moreover, it would be best if your experiments do not interfere with BIP39
to avoid confusion.
That is, your seeds should not be of lengths 12, 15, 18, 21 or 24 words.
--
Best Regards / S pozdravom,
Pavol "Stick" Rusnak
Co-Founder, SatoshiLabs
[-- Attachment #2: Type: text/html, Size: 3323 bytes --]
next prev parent reply other threads:[~2024-01-13 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 14:28 Leslie
2024-01-13 14:12 ` Pavol Rusnak
2024-01-13 15:55 ` Leslie
2024-01-13 16:31 ` Pavol Rusnak [this message]
2024-01-13 17:06 ` Leslie
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='CAF90Av=HqhdOfLpY1Pz8J2N7f_A+L_LDcni2Rx59Z5rNpsLksQ@mail.gmail.com' \
--to=stick@satoshilabs$(echo .)com \
--cc=0300dbdd1b@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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