From: Mike Hearn <mike@plan99•net>
To: slush <slush@centrum•cz>
Cc: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP0039: Final call
Date: Mon, 20 Jan 2014 19:55:04 +0000 [thread overview]
Message-ID: <CANEZrP3sMu1Zp+xhr-D2Nr2Hb+6n0MUkvxvRt64GiAmNzu26Tg@mail.gmail.com> (raw)
In-Reply-To: <CAJna-HjGHpru6Lpv_tXUkWR2mX-=fobzojtHYvSRJy6+CMesOA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1536 bytes --]
We have an implementation of the latest spec in bitcoinj, with the wordlist
provided by slush+stick. As far as I can see it's all working fine so LGTM
from us.
On Mon, Jan 20, 2014 at 5:42 PM, slush <slush@centrum•cz> wrote:
> Hi all,
>
> during recent months we've reconsidered all comments which we received
> from the community about our BIP39 proposal and we tried to meet all
> requirements for such standard. Specifically the proposal now doesn't
> require any specific wordlist, so every client can use its very own list of
> preferred words. Generated mnemonic can be then applied to any other
> BIP39-compatible client. Please follow current draft at
> https://github.com/trezor/bips/blob/master/bip-0039.mediawiki.
>
> Because we're quickly moving towards release of Trezor firmware and we
> need to finalize this part of the firmware, we're asking for the last
> comments to current BIP39 draft.
>
> Thanks,
> slush
>
>
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
[-- Attachment #2: Type: text/html, Size: 2510 bytes --]
next prev parent reply other threads:[~2014-01-20 19:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 17:42 slush
2014-01-20 19:55 ` Mike Hearn [this message]
2014-01-20 20:02 ` Luke-Jr
2014-01-20 21:47 ` slush
2014-01-20 22:01 ` Mark Friedenbach
2014-01-20 22:05 ` Brooks Boyd
2014-01-20 22:35 ` Peter Todd
2014-01-20 23:06 ` Christophe Biocca
2014-01-20 23:18 ` slush
2014-01-21 0:00 ` Thomas Voegtlin
2014-01-24 9:05 ` Peter Todd
2014-01-24 16:47 ` Thomas Voegtlin
2014-01-20 23:14 ` Adam Back
2014-01-20 23:18 ` Mark Friedenbach
[not found] <mailman.423274.1390277261.21953.bitcoin-development@lists.sourceforge.net>
2014-01-21 5:43 ` Tamas Blummer
2014-01-21 10:01 ` Gary Rowe
2014-01-21 10:11 ` Mike Hearn
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=CANEZrP3sMu1Zp+xhr-D2Nr2Hb+6n0MUkvxvRt64GiAmNzu26Tg@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=slush@centrum$(echo .)cz \
/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