public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99.net>
To: Gary Rowe <g.rowe@froot.co.uk>
Cc: Bitcoin Development List <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP0039: Final call
Date: Tue, 21 Jan 2014 10:11:39 +0000	[thread overview]
Message-ID: <CANEZrP0Us2+2_ThvRpy4hvny9i8q8avud5gteXzyJB_C1+m7qQ@mail.gmail.com> (raw)
In-Reply-To: <CAKm8k+0xa5-b=gjfZmH760TbYaQUVf5fGvVK9Jx5jwBGAvcX4g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2127 bytes --]

We should just perform Unicode canonicalization before any text hits the
crypto code.  There are algorithms that automatically resolve such issues.
Although with an English wordlist it would seem to make no difference
anyway.


On Tue, Jan 21, 2014 at 10:01 AM, Gary Rowe <g.rowe@froot.co.uk> wrote:

> MultiBit here.
>
> >At least Trezor and bitcoinj (Multibit) seems to be going in this way,
> >which is 100% of clients which expressed interest in bip39 :-).
> >
> >slush
>
> We'll be using the BIP39 implementation present in Bitcoinj as slush says.
>
> >Proper Unicode handling is a serious issue however. You don't want
> >someone to move from one input method / machine to another and
> >suddenly find that their coins are inaccessible, because of an issue
> >of decomposed vs. compatibility forms or whatever.
>
> We generate the word list internally (12,18,24) and confirm it is entered
> correctly through a retyping operation. This will allow us to detect
> character encoding transpositions (e.g. u0032 vs u00a0) and alert the user
> before it becomes an issue.
>
> While English is the language of the first word list to be implemented, we
> would definitely integrate alternative non-English word lists to make life
> easier for the global community. In general the approach would be for the
> user to select their language (implying a locale) and then the word list to
> be selected from that locale if available with a fallback to English. This
> follows the same approach as resource bundles in Java.
>
>
>
>
> ------------------------------------------------------------------------------
> 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: 3757 bytes --]

  reply	other threads:[~2014-01-21 10:11 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 ` [Bitcoin-development] BIP0039: Final call Tamas Blummer
2014-01-21 10:01   ` Gary Rowe
2014-01-21 10:11     ` Mike Hearn [this message]
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=CANEZrP0Us2+2_ThvRpy4hvny9i8q8avud5gteXzyJB_C1+m7qQ@mail.gmail.com \
    --to=mike@plan99.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=g.rowe@froot.co.uk \
    /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