From: slush <slush@centrum.cz>
To: Pieter Wuille <pieter.wuille@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP0039 Mnemonic code for generating deterministic keys
Date: Thu, 24 Oct 2013 21:46:57 +0200 [thread overview]
Message-ID: <CAJna-HiqD7W3wkF8H7QYaC10xZFDxYFJpJwvyOaa2DUpAYc0QQ@mail.gmail.com> (raw)
In-Reply-To: <CAPg+sBjFAJrDx=dzU3nWCiaUBEiD5fZ2B1aMHGgT1gE402N0Kg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 470 bytes --]
On Thu, Oct 24, 2013 at 9:23 PM, Pieter Wuille <pieter.wuille@gmail.com>wrote:
>
> This is a proposal I wrote a year ago, but never spent enough work to
> push it as a standard:
> https://bitcointalk.org/index.php?topic=102349.0
>
>
I think that PoW concept in your proposal is quite smart! However the
problem that it isn't bidirectional; it don't allow to convert back and
forth between mnemonic and seed, which was one of basic requirement for
such algorithm.
slush
[-- Attachment #2: Type: text/html, Size: 936 bytes --]
next prev parent reply other threads:[~2013-10-24 19:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 16:44 [Bitcoin-development] BIP0039 Mnemonic code for generating deterministic keys slush
2013-09-10 17:36 ` Andreas M. Antonopoulos
2013-09-10 20:40 ` Matthew Mitchell
2013-09-10 20:50 ` slush
2013-09-10 21:03 ` Matthew Mitchell
2013-09-10 21:34 ` Pavol Rusnak
2013-09-10 22:08 ` Gregory Maxwell
2013-09-10 22:35 ` Mark Friedenbach
2013-09-10 22:43 ` Gregory Maxwell
2013-09-11 12:49 ` Andreas Petersson
2013-09-12 12:09 ` Pavol Rusnak
2013-09-10 22:47 ` slush
2013-09-12 12:11 ` Pavol Rusnak
2013-09-12 16:02 ` Matthew Mitchell
2013-10-24 18:26 ` slush
2013-10-24 19:23 ` Pieter Wuille
2013-10-24 19:46 ` slush [this message]
2013-10-24 19:32 ` Jorge Timón
2013-10-24 19:37 ` slush
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=CAJna-HiqD7W3wkF8H7QYaC10xZFDxYFJpJwvyOaa2DUpAYc0QQ@mail.gmail.com \
--to=slush@centrum.cz \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=pieter.wuille@gmail.com \
/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