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
|
Return-Path: <keatonatron@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id C639CE22
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 26 Dec 2018 18:54:54 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wr1-f44.google.com (mail-wr1-f44.google.com
[209.85.221.44])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 488C7189
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 26 Dec 2018 18:54:54 +0000 (UTC)
Received: by mail-wr1-f44.google.com with SMTP id x10so16341311wrs.8
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 26 Dec 2018 10:54:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to
:cc; bh=kHuLPXGO9b7tfNbhpHHEDZ4p2YLu9j/cYFgaIIwtH6g=;
b=XRFGO6CPFoWqGP0ZzUZRC5JaPTKKUW/9TY0MT51i8YYDbI75HTkjAuO7+IY5vCIhob
S37VAdB++XPStugFcM4PRH0dAs7cDMojazh4SDT7JuWtXG6qAU8CMluqmI7XSPQsCDBq
0CVOLyopuNETcsxjJjHgUDFJw6tI2JmK9dIXP08I0CnSJC7A+bgJlj+YwrwaG6JoqGPV
mbtvwNvo17sY1gr/fPZwU+83XopDil58hgXhsJJsk/YAsFHm5EG+uDl8gVNo4x3hueom
azzGh0TKz9G/SGpmspOyBeQika6deXZ/qLDSuhzSNH8STriazJMyIxYytihAQMycVHVm
iqQA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to:cc;
bh=kHuLPXGO9b7tfNbhpHHEDZ4p2YLu9j/cYFgaIIwtH6g=;
b=HjZM/zuIo4u42v6p7DCN7qxt40d2surKIbxg2QbWhbOE12AD1Vt6Z7o2hHs255J9Ie
ycaf2d4FGJWWk1wA4U3N4UrGGgUB0SAw48R6CrxsgUf0vs081LFQwd+546YCz4v93yqv
oltro0ejIqRL+kSfSkNsDWEVkgbcpU8WlazWhElYdJ4ngftGylPGQSypeEEaS4io+XrP
ek820XzkqMpf9004K4cerrPgEPXTfp2PFT2ARdfhbI8nU9mAidpKDWCiU9G80EIqww+K
sn6fCGtFw6VusovMEt+uFBLUr1w2lHEwKf05ACbkx+bAtpsjAa24WevukxTzOavw4naT
aDng==
X-Gm-Message-State: AJcUukedUw5h5pWvlsrvDn5RsUjatJsRbEZco/g3V4zlmvavKO+ZF9b4
jTU0ORWpzanOEB9YyzVwe5soxkdl3SFWLBPBtSY=
X-Google-Smtp-Source: ALg8bN5oRu+uPutKShJzbiCNB8Lg0K+ms1G9eM5caXkuiotBVoTO4qljYPaNIwWV4GxFG6Z3UrD+AjdgJrKsLxfSOXI=
X-Received: by 2002:adf:e707:: with SMTP id c7mr18267321wrm.196.1545850492659;
Wed, 26 Dec 2018 10:54:52 -0800 (PST)
MIME-Version: 1.0
References: <68330522-7e7c-c3b4-99a9-1c68ddb56f23@gmail.com>
<f2d73a92-e1c5-9072-e255-fa012a9f9d1b@satoshilabs.com>
<db184306-7ec0-322e-5637-7889b51f50bf@gmail.com>
<CAH+Axy6dKDOkE6cQYZUusTUxxOSwWchOWxYh6ZkhnOgXuELaYg@mail.gmail.com>
<743fb106-977e-1f34-47af-9fb3b8621e72@gmail.com>
In-Reply-To: <743fb106-977e-1f34-47af-9fb3b8621e72@gmail.com>
From: James MacWhyte <macwhyte@gmail.com>
Date: Wed, 26 Dec 2018 18:54:25 +0000
Message-ID: <CAH+Axy7v=26P8=CJPUqymKOcromGz+zYZ2cb2KaASgXNPpE2tQ@mail.gmail.com>
To: Aymeric VITTE <vitteaymeric@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000007dae87057df15d7c"
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Thu, 27 Dec 2018 14:59:24 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP39 seeds
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
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: Wed, 26 Dec 2018 18:54:54 -0000
--0000000000007dae87057df15d7c
Content-Type: text/plain; charset="UTF-8"
On Wed, Dec 26, 2018 at 11:33 AM Aymeric Vitte <vitteaymeric@gmail.com>
wrote:
> so, even with a tool like yours, they can be misleaded, for example trying
> a few words to replace the missing/incorrect one, get a valid seed and stay
> stuck with it forever trying to play with BIP44/49 to find their keys
>
Just a small detail, but my tool actually looks up all the possible
combinations and then finds which one has been used before by looking for
past transactions on the blockchain. Therefore, it won't tell you your
phrase is correct unless it is a phrase that has actually been used before
(preventing what you described).
Using some algorithm to take some input and generate a bip39 phrase that
you can use with any bip39 wallet sounds perfectly reasonable.
--0000000000007dae87057df15d7c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div dir=3D"ltr" class=3D"gmail_signature" data-smart=
mail=3D"gmail_signature"><div dir=3D"ltr"><br></div></div></div><div class=
=3D"gmail_quote"><div dir=3D"ltr">On Wed, Dec 26, 2018 at 11:33 AM Aymeric =
Vitte <<a href=3D"mailto:vitteaymeric@gmail.com">vitteaymeric@gmail.com<=
/a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
=20
=20
=20
<div bgcolor=3D"#FFFFFF">
<p>so, even with a tool like yours, they can be misleaded, for
example trying a few words to replace the missing/incorrect one,
get a valid seed and stay stuck with it forever trying to play
with BIP44/49 to find their keys<br></p></div></blockquote><div><br><=
/div><div>Just a small detail, but my tool actually looks up all the possib=
le combinations and then finds which one has been used before by looking fo=
r past transactions on the blockchain. Therefore, it won't tell you you=
r phrase is correct unless it is a phrase that has actually been used befor=
e (preventing what you described).</div><div><br></div><div>Using some algo=
rithm to take some input and generate a bip39 phrase that you can use with =
any bip39 wallet sounds perfectly reasonable.</div></div></div>
--0000000000007dae87057df15d7c--
|
