public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Bram Cohen <bram@chia.net>
To: Anton Shevchenko <anton@sancoder.com>,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] No Order Mnemonic
Date: Thu, 7 Jul 2022 10:36:26 -0700	[thread overview]
Message-ID: <CAHUJnBAL-qPoGZ8XZS3jZiPaqMOt4Kg2ioM_jfCF3fDB3-ej9A@mail.gmail.com> (raw)
In-Reply-To: <0dc0e945-9e12-43ad-bd12-fcc0e18e4013@www.fastmail.com>

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

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.

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

  reply	other threads:[~2022-07-07 17:36 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 [this message]
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
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=CAHUJnBAL-qPoGZ8XZS3jZiPaqMOt4Kg2ioM_jfCF3fDB3-ej9A@mail.gmail.com \
    --to=bram@chia.net \
    --cc=anton@sancoder.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