From: Tamas Blummer <tamas@bitsofproof•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] BIP0039: Final call
Date: Tue, 21 Jan 2014 06:43:49 +0100 [thread overview]
Message-ID: <300D31FC-FB89-4386-8DD9-F5FA792D0B40@bitsofproof.com> (raw)
In-Reply-To: <mailman.423274.1390277261.21953.bitcoin-development@lists.sourceforge.net>
[-- Attachment #1.1: Type: text/plain, Size: 491 bytes --]
> At least Trezor and bitcoinj (Multibit) seems to be going in this way,
> which is 100% of clients which expressed interest in bip39 :-).
>
> slush
The the current spec with TREZOR's wordlist is also implemented by Bits of Proof
https://github.com/bitsofproof/supernode/blob/master/api/src/main/java/com/bitsofproof/supernode/wallet/BIP39.java
and deployed in two projects, one being btc1k also open sourced at our github.
Regards,
Tamás Blummer
http://bitsofproof.com
[-- Attachment #1.2: Type: text/html, Size: 4267 bytes --]
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next parent reply other threads:[~2014-01-21 6:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.423274.1390277261.21953.bitcoin-development@lists.sourceforge.net>
2014-01-21 5:43 ` Tamas Blummer [this message]
2014-01-21 10:01 ` Gary Rowe
2014-01-21 10:11 ` Mike Hearn
2014-01-20 17:42 slush
2014-01-20 19:55 ` Mike Hearn
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
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=300D31FC-FB89-4386-8DD9-F5FA792D0B40@bitsofproof.com \
--to=tamas@bitsofproof$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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