public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: James MacWhyte <macwhyte@gmail•com>
To: Paul Sztorc <truthcoin@gmail•com>,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] No Order Mnemonic
Date: Fri, 8 Jul 2022 16:08:54 +0200	[thread overview]
Message-ID: <CAH+Axy4X+uQG5Vw0Efiz6AtNyK=++h-jDeZL1ZxpVJus8BVKeA@mail.gmail.com> (raw)
In-Reply-To: <CA+XQW1iKVRmEnyP-CGM2Fo4qHi3SQHUfjEmKftDdju-uxHViJg@mail.gmail.com>

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

> What do you do if the "first" word (of 12), happens to be the last word in
> the list alphabetically?
>

That couldn't happen. If one word is the very last from the wordlist, it
would end up at the end of your mnemonic once you rearrange your 12 words
alphabetically.

However!

(@vjudeu) Choosing 11 random words and then sorting them alphabetically
before assigning a checksum would reduce entropy considerably. If you think
about it, to bruteforce the entire keyspace one would only need to come up
with every possible combination of 11 words + 1 checksum. I'm not the best
at napkin math, but I think that leaves you with around 10 trillion
combinations, which would only take a couple months to exhaust with
hardware that can do 1 million guesses per second.

James

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

  reply	other threads:[~2022-07-08 14:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07 14:33 Anton Shevchenko
2022-07-07 17:36 ` Bram Cohen
2022-07-07 17:52   ` Pavol Rusnak
2022-07-07 17:58     ` Anton Shevchenko
2022-07-08  1:47     ` Bram Cohen
2022-07-08  2:19       ` Eric Voskuil
2022-07-08  4:35         ` vjudeu
2022-07-08  9:12           ` Paul Sztorc
2022-07-08 14:08             ` James MacWhyte [this message]
2022-07-09 20:31               ` Zac Greenwood
2022-07-09 22:21                 ` James MacWhyte
2022-07-09 23:46                 ` Anton Shevchenko
2022-07-11 13:11                   ` Erik Aronesty
2022-07-11 13:18                     ` Erik Aronesty

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='CAH+Axy4X+uQG5Vw0Efiz6AtNyK=++h-jDeZL1ZxpVJus8BVKeA@mail.gmail.com' \
    --to=macwhyte@gmail$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=truthcoin@gmail$(echo .)com \
    /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