From: "Anton Shevchenko" <anton@sancoder.com>
To: "Pavol Rusnak" <stick@satoshilabs.com>,
"Alfred Hodler" <bitcoin-dev@lists.linuxfoundation.org>,
"Bram Cohen" <bram@chia.net>
Subject: Re: [bitcoin-dev] No Order Mnemonic
Date: Thu, 07 Jul 2022 10:58:40 -0700 [thread overview]
Message-ID: <68d39c5e-bd31-44e5-a5dc-e63d496ee780@www.fastmail.com> (raw)
In-Reply-To: <CAF90AvmOSa+V7+z16MXyJRCVh_iEceFp_CkbC_4jWixi4W5BbQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]
But this will require user to distinguish 12 words from error correcting words. Which is another hassle.
On Thu, Jul 7, 2022, at 10:52 AM, Pavol Rusnak wrote:
> There is. Just encode the index of permutation used to scramble the otherwise sorted list. For 12 words you need to store 12! = ~32 bits so 3 words should be enough.
>
> Repetitions make this more difficult, though.
>
> On Thu 7. 7. 2022 at 19:41, Bram Cohen via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
>> On Thu, Jul 7, 2022 at 7:43 AM Anton Shevchenko via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
>>> I made a python implementation for a different mnemonic encoding. The encoding requires user to remember words but not the order of those words.
>>> The code is open (MIT license) at https://github.com/sancoder/noomnem
>>
>> Thanks Anton. There's an interesting mathematical question of whether it's possible to make a code like this which always uses the BIP-39 words for the same key as part of its encoding, basically adding a few words as error correction in case the order is lost or confused. If the BIP-39 contains a duplicate you can add an extra word.
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> --
>
> Best Regards / S pozdravom,
>
> Pavol "stick" Rusnak
> Co-Founder, SatoshiLabs
[-- Attachment #2: Type: text/html, Size: 3225 bytes --]
next prev parent reply other threads:[~2022-07-07 17:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 14:33 [bitcoin-dev] No Order Mnemonic Anton Shevchenko
2022-07-07 17:36 ` Bram Cohen
2022-07-07 17:52 ` Pavol Rusnak
2022-07-07 17:58 ` Anton Shevchenko [this message]
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
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=68d39c5e-bd31-44e5-a5dc-e63d496ee780@www.fastmail.com \
--to=anton@sancoder.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=bram@chia.net \
--cc=stick@satoshilabs.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