public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Pavol Rusnak <stick@gk2.sk>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP0039 Mnemonic code for generating deterministic keys
Date: Tue, 10 Sep 2013 23:34:01 +0200	[thread overview]
Message-ID: <522F9049.3020703@gk2.sk> (raw)
In-Reply-To: <0F445FFE-FA1A-4A64-9A28-C734E744B5F7@godofgod.co.uk>

On 10/09/13 23:03, Matthew Mitchell wrote:
> Maybe it would have been better without the aggressive words?

Feel free to come up with wordlist enhancements. That's why we put
this BIP for discussion in the first place. Three people went through
the wordlist numerous number of times and as you can see it's still
not perfect.

Please bear in mind that for every word you remove from the list, you
have to come up with a good alternative that is unique and hard to
confuse with the others.

-- 
Best Regards / S pozdravom,

Pavol Rusnak <stick@gk2.sk>



  reply	other threads:[~2013-09-10 21:55 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 [this message]
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
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=522F9049.3020703@gk2.sk \
    --to=stick@gk2.sk \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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