summaryrefslogtreecommitdiff
path: root/3f/8bfcac0318bfeb4d98420dbe25b86ff5121f61
blob: ae6a84c831ac0e494565743368c173f81ac93045 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
Return-Path: <vjudeu@gazeta.pl>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137])
 by lists.linuxfoundation.org (Postfix) with ESMTP id B1120C002D
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri,  8 Jul 2022 04:35:30 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp4.osuosl.org (Postfix) with ESMTP id 6BECA4241D
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri,  8 Jul 2022 04:35:30 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 6BECA4241D
Authentication-Results: smtp4.osuosl.org;
 dkim=pass (1024-bit key) header.d=gazeta.pl header.i=@gazeta.pl
 header.a=rsa-sha256 header.s=2013 header.b=tR84oi+s
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
 SPF_HELO_NONE=0.001, SPF_PASS=-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 fAEClg3xqsWv
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri,  8 Jul 2022 04:35:29 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org A51F2423E1
Received: from smtpo43.poczta.onet.pl (smtpo43.poczta.onet.pl
 [213.180.142.174])
 by smtp4.osuosl.org (Postfix) with ESMTPS id A51F2423E1
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri,  8 Jul 2022 04:35:28 +0000 (UTC)
Received: from pmq5v.m5r2.onet (pmq5v.m5r2.onet [10.174.35.25])
 by smtp.poczta.onet.pl (Onet) with ESMTP id 4LfL6w1lX0zlWp;
 Fri,  8 Jul 2022 06:35:20 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gazeta.pl; s=2013;
 t=1657254920; bh=tb04W2RhkjIMm+tc6xZYoH8P8OHBoEu3BcPFJizFBsw=;
 h=From:To:In-Reply-To:Date:Subject:From;
 b=tR84oi+sm9FWbYlX498rZJSlpWKr2qByho2jBbxKd9kXiCmJ1qDq0Swc3H3dfGUOD
 0U/1TP8jcBmK6ZL71G1WPOTS+7z5T+HhRjs88h7u63vN3/jbLmjp1kE4ReCxdoq3QC
 Stmw/P/U+/5i6ctNto+EQ6XJ/Q2lCUOQKMBboxtw=
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Received: from [5.173.241.111] by pmq5v.m5r2.onet via HTTP id ;
 Fri, 08 Jul 2022 06:35:20 +0200
From: vjudeu@gazeta.pl
X-Priority: 3
To: "Eric Voskuil <eric@voskuil.org>,
 Bitcoin Protocol Discussion" <bitcoin-dev@lists.linuxfoundation.org>,
 Bram Cohen <bram@chia.net>,
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
In-Reply-To: <3D3BFE9C-CFF3-49FF-840F-063B52C69A42@voskuil.org>
Date: Fri, 08 Jul 2022 06:35:16 +0200
Message-Id: <164256450-0ee6752f92c0be297952fc72b59076df@pmq5v.m5r2.onet>
X-Mailer: onet.poczta
X-Onet-PMQ: <vjudeu@gazeta.pl>;5.173.241.111;PL;2
X-Mailman-Approved-At: Fri, 08 Jul 2022 08:48:24 +0000
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 04:35:30 -0000

Isn't it enough to just generate a seed in the same way as today, then sort=
 the words alphabetically, and then use that as a seed? I know, the last wo=
rd is a checksum, but there are only 2048 words, so it is not a big deal to=
 get any checksum we want. If that is insecure, because of lower possible c=
ombinations, then it is always possible to increase the number of words to =
compensate that.


On 2022-07-08 04:27:21 user Eric Voskuil via bitcoin-dev <bitcoin-dev@lists=
.linuxfoundation.org> wrote:


Without a performance requirement there is no reason you can=E2=80=99t stor=
e the BIP39 words in any order you want. So it=E2=80=99s certainly possible=
, just brute force the recovery. If you have less than a second vs. a few d=
ays then it=E2=80=99s a different question.


e


On Jul 7, 2022, at 18:48, Bram Cohen via bitcoin-dev <bitcoin-dev@lists.lin=
uxfoundation.org> wrote:
Part of the rules of my challenge is that the 'new' words need to be in the=
 same pool as the 'old' words, so any ordering is okay. Without that requir=
ement it's mathematically very straightforward.


On Thu, Jul 7, 2022 at 10:52 AM Pavol Rusnak <stick@satoshilabs.com> wrote:
There is. Just encode the index of permutation used to scramble the otherwi=
se sorted list. For 12 words you need to store 12! =3D ~32 bits so 3 words =
should be enough.=C2=A0


Repetitions make this more difficult, though.=C2=A0


On Thu 7. 7. 2022 at 19:41, Bram Cohen via bitcoin-dev <bitcoin-dev@lists.l=
inuxfoundation.org> wrote:
On Thu, Jul 7, 2022 at 7:43 AM Anton Shevchenko via bitcoin-dev <bitcoin-de=
v@lists.linuxfoundation.org> wrote:
I made a python implementation for a different mnemonic encoding. The encod=
ing 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 th=
e 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 d=
uplicate you can add an extra word.
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev