path: root/87/82c64deea9218f0dbc43e1fcfc3746e924568a

Return-Path: <eric@voskuil.org>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 63482C002D
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri,  8 Jul 2022 02:19:48 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp4.osuosl.org (Postfix) with ESMTP id 2E8894246A
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri,  8 Jul 2022 02:19:48 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 2E8894246A
Authentication-Results: smtp4.osuosl.org;
 dkim=pass (2048-bit key) header.d=voskuil-org.20210112.gappssmtp.com
 header.i=@voskuil-org.20210112.gappssmtp.com header.a=rsa-sha256
 header.s=20210112 header.b=62gO8gYX
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001,
 RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001]
 autolearn=ham autolearn_force=no
Received: from smtp4.osuosl.org ([127.0.0.1])
 by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id T-zplkG7IJKE
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri,  8 Jul 2022 02:19:46 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 85AAF4245E
Received: from mail-pg1-x52b.google.com (mail-pg1-x52b.google.com
 [IPv6:2607:f8b0:4864:20::52b])
 by smtp4.osuosl.org (Postfix) with ESMTPS id 85AAF4245E
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri,  8 Jul 2022 02:19:46 +0000 (UTC)
Received: by mail-pg1-x52b.google.com with SMTP id bh13so15252810pgb.4
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu, 07 Jul 2022 19:19:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=voskuil-org.20210112.gappssmtp.com; s=20210112;
 h=content-transfer-encoding:from:mime-version:subject:date:message-id
 :references:cc:in-reply-to:to;
 bh=GMmejxqrzq65JhRjUcU1bqNhsn/16i8mDfHacsKQ9Os=;
 b=62gO8gYXUVmz4+i2q/+b7ecZ6yoTI6ocBvzX2txgQXhM+E4exXCtqY2qG06ixzZMVC
 nFFEJpKBVn+dXz65xkc1VICWBd7aSwjSkv7QJPdQW/lSAhVg/XPH7DZM5tPlvliXeths
 0KM/gv8JlVIQAOgCjP/480UprCXICjGMS78Fdycjv4mh7Di5YPKwmNErwcPO4dBcCHHP
 Pc58A4eHgRH/IPORMab+UReicm3J4HXCbCxJ8tlXZ8TRcVfI1+DbWh97E7Os1hWWKAXE
 VZSVAXjoG4wgQKp1hBngmlgBAPO72xTBGoINjOQO/ni9SdwA6sIKLhySKCeXz4PnXfpe
 oDwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:content-transfer-encoding:from:mime-version
 :subject:date:message-id:references:cc:in-reply-to:to;
 bh=GMmejxqrzq65JhRjUcU1bqNhsn/16i8mDfHacsKQ9Os=;
 b=oqbYOwj/FHOW6t4GiLMiCZgahQW43MGdGnK0ZyoN192eGh9wTZff9JPZ75n7rv6Zsh
 iRX8Fl4RfoxU4dQmIzDPJeTFjhS/f1I0P8E/RLwcTv0uComt+7j1WAleOsfcmftbuiBI
 lQ3R8zA8kIS0FgS3aBTzWDeKSVXZ3JRIDFz5vzwC/+6yjlGyD6ELsvB3i1UN5J5NrUVQ
 OtenAxeZibeFfQXZdehT6tX2qxg0jz8uj51Igslu4Rye/GRdNpxN0QYABax6aIvPNmQl
 doReRWFVyHihHIiuZpVQeKKUgVtrY8TGBFTb69tAzds2EHZW8xNF8hPv2IqqopfoYD2o
 oRrQ==
X-Gm-Message-State: AJIora+G5avywueTZP1CXvDBiuv+Lovxqj+7yof9ByJB2CrFJsiJALod
 ZammvohQLs5j5ybC83jMpbz4oer3n0gJnw==
X-Google-Smtp-Source: AGRyM1t3xPeXKbVJEffWmsSvA61V3Wl8+nF7IWwTxh2VEkXzowbg35zB2t5y5ClB7dLNa9egu/Y26Q==
X-Received: by 2002:a05:6a00:234f:b0:525:1f7c:f2bf with SMTP id
 j15-20020a056a00234f00b005251f7cf2bfmr1165372pfj.14.1657246785588; 
 Thu, 07 Jul 2022 19:19:45 -0700 (PDT)
Received: from smtpclient.apple ([2600:380:801f:6202:f47e:c7ca:fad6:7d1])
 by smtp.gmail.com with ESMTPSA id
 c28-20020a631c1c000000b0041291dba64asm4015075pgc.26.2022.07.07.19.19.44
 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
 Thu, 07 Jul 2022 19:19:44 -0700 (PDT)
Content-Type: multipart/alternative;
 boundary=Apple-Mail-3F00B8F3-6D38-4F92-82F8-FD6B164E9037
Content-Transfer-Encoding: 7bit
From: Eric Voskuil <eric@voskuil.org>
Mime-Version: 1.0 (1.0)
Date: Thu, 7 Jul 2022 19:19:43 -0700
Message-Id: <3D3BFE9C-CFF3-49FF-840F-063B52C69A42@voskuil.org>
References: <CAHUJnBCHZ7+6B83xDOaSc+EEpVe2x4VzmZUTQ3Z7FhmtMQFbjA@mail.gmail.com>
In-Reply-To: <CAHUJnBCHZ7+6B83xDOaSc+EEpVe2x4VzmZUTQ3Z7FhmtMQFbjA@mail.gmail.com>
To: Bram Cohen <bram@chia.net>,
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
X-Mailer: iPhone Mail (19F77)
Subject: Re: [bitcoin-dev] No Order Mnemonic
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2022 02:19:48 -0000


--Apple-Mail-3F00B8F3-6D38-4F92-82F8-FD6B164E9037
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

Without a performance requirement there is no reason you can=E2=80=99t store=
 the BIP39 words in any order you want. So it=E2=80=99s certainly possible, j=
ust brute force the recovery. If you have less than a second vs. a few days t=
hen it=E2=80=99s a different question.

e

> On Jul 7, 2022, at 18:48, Bram Cohen via bitcoin-dev <bitcoin-dev@lists.li=
nuxfoundation.org> wrote:
> =EF=BB=BF
> Part of the rules of my challenge is that the 'new' words need to be in th=
e same pool as the 'old' words, so any ordering is okay. Without that requir=
ement it's mathematically very straightforward.
>=20
>> On Thu, Jul 7, 2022 at 10:52 AM Pavol Rusnak <stick@satoshilabs.com> wrot=
e:
>> There is. Just encode the index of permutation used to scramble the other=
wise sorted list. For 12 words you need to store 12! =3D ~32 bits so 3 words=
 should be enough.=20
>>=20
>> Repetitions make this more difficult, though.=20
>>=20
>>> On Thu 7. 7. 2022 at 19:41, Bram Cohen via bitcoin-dev <bitcoin-dev@list=
s.linuxfoundation.org> wrote:
>>>> On Thu, Jul 7, 2022 at 7:43 AM Anton Shevchenko via bitcoin-dev <bitcoi=
n-dev@lists.linuxfoundation.org> wrote:
>>>=20
>>>> I made a python implementation for a different mnemonic encoding. The e=
ncoding requires user to remember words but not the order of those words.
>>>> The code is open (MIT license) at https://github.com/sancoder/noomnem
>>>=20
>>> 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 t=
he same key as part of its encoding, basically adding a few words as error c=
orrection in case the order is lost or confused. If the BIP-39 contains a du=
plicate you can add an extra word.
>>> _______________________________________________
>>> bitcoin-dev mailing list
>>> bitcoin-dev@lists.linuxfoundation.org
>>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>> --=20
>> Best Regards / S pozdravom,
>>=20
>> Pavol "stick" Rusnak
>> Co-Founder, SatoshiLabs
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

--Apple-Mail-3F00B8F3-6D38-4F92-82F8-FD6B164E9037
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div dir=3D"ltr"></div><div dir=3D"ltr">Wit=
hout a performance requirement there is no reason you can=E2=80=99t store th=
e BIP39 words in any order you want. So it=E2=80=99s certainly possible, jus=
t brute force the recovery. If you have less than a second vs. a few days th=
en it=E2=80=99s a different question.</div><div dir=3D"ltr"><br></div><div d=
ir=3D"ltr">e</div><div dir=3D"ltr"><br><blockquote type=3D"cite">On Jul 7, 2=
022, at 18:48, Bram Cohen via bitcoin-dev &lt;bitcoin-dev@lists.linuxfoundat=
ion.org&gt; wrote:<br></blockquote></div><blockquote type=3D"cite"><div dir=3D=
"ltr">=EF=BB=BF<div dir=3D"ltr">Part of the rules of my challenge is that th=
e 'new' words need to be in the same pool as the 'old' words, so any orderin=
g is okay. Without that requirement it's mathematically very straightforward=
.</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">=
On Thu, Jul 7, 2022 at 10:52 AM Pavol Rusnak &lt;<a href=3D"mailto:stick@sat=
oshilabs.com">stick@satoshilabs.com</a>&gt; wrote:<br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div dir=3D"auto">There is. Just encode the=
 index of permutation used to scramble the otherwise sorted list. For 12 wor=
ds you need to store 12! =3D ~32 bits so 3 words should be enough.&nbsp;</di=
v><div dir=3D"auto"><br></div><div dir=3D"auto">Repetitions make this more d=
ifficult, though.&nbsp;</div><div><br><div class=3D"gmail_quote"><div dir=3D=
"ltr" class=3D"gmail_attr">On Thu 7. 7. 2022 at 19:41, Bram Cohen via bitcoi=
n-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D=
"_blank">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br></div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr=
">On Thu, Jul 7, 2022 at 7:43 AM Anton Shevchenko via bitcoin-dev &lt;<a hre=
f=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoin=
-dev@lists.linuxfoundation.org</a>&gt; wrote:<br></div><div class=3D"gmail_q=
uote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left:1px solid rgb(204,204,204);padding-left:1ex">I made a python imple=
mentation for a different mnemonic encoding. The encoding requires user to r=
emember words but not the order of those words.<br>
The code is open (MIT license) at <a href=3D"https://github.com/sancoder/noo=
mnem" rel=3D"noreferrer" target=3D"_blank">https://github.com/sancoder/noomn=
em</a></blockquote><div><br></div><div>Thanks Anton. There's an interesting m=
athematical 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, basi=
cally adding a few words as error correction in case the order is lost or co=
nfused. If the BIP-39 contains a duplicate you can add an extra word.</div><=
/div></div>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">b=
itcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" r=
el=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mailma=
n/listinfo/bitcoin-dev</a><br>
</blockquote></div></div>-- <br><div dir=3D"ltr"><div dir=3D"ltr"><div><div d=
ir=3D"ltr"><div></div><div>Best Regards / S pozdravom,</div><div><br></div><=
div>Pavol "stick" Rusnak</div><div>Co-Founder, SatoshiLabs</div></div></div>=
</div></div>
</blockquote></div>
<span>_______________________________________________</span><br><span>bitcoi=
n-dev mailing list</span><br><span>bitcoin-dev@lists.linuxfoundation.org</sp=
an><br><span>https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev<=
/span><br></div></blockquote></body></html>=

--Apple-Mail-3F00B8F3-6D38-4F92-82F8-FD6B164E9037--