From: Aymeric Vitte <vitteaymeric@gmail•com>
To: James MacWhyte <macwhyte@gmail•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP39 seeds
Date: Thu, 27 Dec 2018 12:04:18 +0100 [thread overview]
Message-ID: <c91cd61b-3ec5-6c7a-c7e3-7ceb48539625@gmail.com> (raw)
In-Reply-To: <CAH+Axy7v=26P8=CJPUqymKOcromGz+zYZ2cb2KaASgXNPpE2tQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1674 bytes --]
Le 26/12/2018 à 19:54, James MacWhyte a écrit :
>
> On Wed, Dec 26, 2018 at 11:33 AM Aymeric Vitte <vitteaymeric@gmail•com
> <mailto: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).
I saw that your tool was querying blockchain.info, but it cannot guess
what derivation path was used and if it is a standard one what addresses
were used, and even if successful it works only for bitcoin (so maybe it
should just output the ~1500 possible phrases and/or xprv, and be
completely offline, this is still doable for people)
>
> Using some algorithm to take some input and generate a bip39 phrase
> that you can use with any bip39 wallet sounds perfectly reasonable.
I forgot to mention that this can help also solving the "what if
something happens to me" case giving to the family the seed and the
parameter(s) for the derivation path, or an easy way to find it (better
than something like: remind this passphrase, take the sha256 of it, then
use some other stuff to find the encryption algo, take n bytes of the
hash, use it to decode my wallet or my seed... and then everybody
looking at you like crazy)
[-- Attachment #2: Type: text/html, Size: 3295 bytes --]
next prev parent reply other threads:[~2018-12-27 11:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 23:58 Aymeric Vitte
2018-12-23 18:46 ` Pavol Rusnak
2018-12-23 22:41 ` Aymeric Vitte
2018-12-25 0:30 ` James MacWhyte
2018-12-26 11:33 ` Aymeric Vitte
2018-12-26 18:54 ` James MacWhyte
2018-12-27 11:04 ` Aymeric Vitte [this message]
2018-12-31 16:52 ` Alan Evans
2019-01-01 19:44 ` Aymeric Vitte
2019-01-02 18:06 ` James MacWhyte
2019-01-04 0:02 ` Aymeric Vitte
2018-12-24 14:58 ` Tiago Romagnani Silveira
2018-12-23 20:55 ` Eric Scrivner
2018-12-23 21:08 ` Jameson Lopp
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=c91cd61b-3ec5-6c7a-c7e3-7ceb48539625@gmail.com \
--to=vitteaymeric@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=macwhyte@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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