From: Jameson Lopp <jameson.lopp@gmail.com>
To: dr.oso.phila.cgeyb@aleeas.com
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] BIP Idea: Scrambling BIP39 recovery seeds
Date: Tue, 31 Mar 2026 08:37:38 +0200 [thread overview]
Message-ID: <CADL_X_d2h_qiNfw0qcH9ii681_8raCX1M0mpyOuFB_2xbw=2zw@mail.gmail.com> (raw)
In-Reply-To: <177470526996.8.13158104493925689779.1256635257@aleeas.com>
[-- Attachment #1: Type: text/plain, Size: 2393 bytes --]
Have you read BIP39 in detail?
It sounds like you're inventing an alternative to the passphrase protection
described here:
https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki#from-mnemonic-to-seed
On Sat, Mar 28, 2026 at 2:54 PM dr.oso.phila.cgeyb via Bitcoin Development
Mailing List <bitcoindev@googlegroups.com> wrote:
> Dear Developers
>
> Thank you for dedicating your time on a thrilling project - Bitcoin.
>
> Recently, this idea came into my mind. I tried to summarize and write it
> down as clear as possible, following BIP3, which states:
> "As a first sketch of the proposal is taking shape, the authors should
> present it to the Bitcoin Development Mailing List. This gives the
> authors a chance to collect initial feedback and address fundamental
> concerns."
> I refrained from forking the github bitcoin/bips tree just to upload one
> properly formatted document. I am no programmer and unfamiliar to the
> world of bitcoin developers, so forgive me if I do things which seem
> strange to you.
>
> The main question about this idea is: does a suitable function exists? I
> thought of discrete exponentiation. But as a former math student, I
> remember that this does not always work as expected beforehand...
> All I know that a similar concept is used in Diffie-Hellman Key Exchange
> and you're more into cryptography as I am. Therefore I thought that it's
> best to ask this question to you. Maybe you have a better idea.
>
> If no idea comes up, well... then it's a dead end.
>
> Best
> Dr. Oso Phila, a small bug
>
> --
> 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/177470526996.8.13158104493925689779.1256635257%40aleeas.com
> .
>
--
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/CADL_X_d2h_qiNfw0qcH9ii681_8raCX1M0mpyOuFB_2xbw%3D2zw%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 3401 bytes --]
prev parent reply other threads:[~2026-03-31 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-28 13:41 dr.oso.phila.cgeyb via Bitcoin Development Mailing List
2026-03-31 6:37 ` Jameson Lopp [this message]
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='CADL_X_d2h_qiNfw0qcH9ii681_8raCX1M0mpyOuFB_2xbw=2zw@mail.gmail.com' \
--to=jameson.lopp@gmail.com \
--cc=bitcoindev@googlegroups.com \
--cc=dr.oso.phila.cgeyb@aleeas.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