MIME-Version: 1.0
References: <bANNM0nNJ1cJdrNjvBZfx6O-zwAQ_bg4qPgoYCQGGNQxc0I4AHF0nQCqPYGqYQzLMP07URApaPCOBBPC4whZ77M8amvUdfIo3TFhQjpzNpY=@protonmail.com>
	<CAMpN3m+Zo6LG1wCkW7tLZy7VzpF8YpjHQqq7StO78C0P-8y0Ew@mail.gmail.com>
	<20181116140335.GA11584@boiler.chaos.net>
In-Reply-To: <20181116140335.GA11584@boiler.chaos.net>
From: Jonathan Underwood <junderwood@bitcoinbank.co.jp>
Date: Fri, 16 Nov 2018 23:05:50 +0900
Message-ID: <CAMpN3mLRUD+cobNHtK=5dCL2hpGZJaR2TYzKb_643BC-wM5feQ@mail.gmail.com>
To: Neill Miller <neillm@thecodefactory.org>
Content-Type: multipart/alternative; boundary="000000000000e7d62d057ac8aa5f"
Cc: bitcoin-dev@lists.linuxfoundation.org, somber.night@protonmail.com
Subject: Re: [bitcoin-dev] BIP- & SLIP-0039 -- better multi-language support
Precedence: list

--000000000000e7d62d057ac8aa5f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Nope.

This is how Electrum treats BIP39 restoring as well, try it out.

-Jon

2018=E5=B9=B411=E6=9C=8816=E6=97=A5(=E9=87=91) 23:04=E3=80=81Neill Miller =
=E3=81=95=E3=82=93=EF=BC=88neillm@thecodefactory.org=EF=BC=89=E3=81=AE=E3=
=83=A1=E3=83=83=E3=82=BB=E3=83=BC=E3=82=B8:

> On Fri, Nov 09, 2018 at 02:17:30PM +0900, Jonathan Underwood via
> bitcoin-dev wrote:
> > If more apps would implement to the word of the BIP39 spec, multiple
> > languages make sense, but since reality is no one follows the spec (/th=
e
> > spec is way too open to interpretation) then expecting every app to loa=
d
> > every language is unreasonable.
> >
> > Electrum actually handles BIP39 recovery the way the BIP specifies. I c=
an
> > restore random strings if I want, and it warns me, and I can ignore it
> if I
> > wish.
>
> Electrum mnemonics are not based on BIP39, which is why it can do
> this.
>
> -Neill.
>
>

--000000000000e7d62d057ac8aa5f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Nope.<div dir=3D"auto"><br></div><div dir=3D"auto">This i=
s how Electrum treats BIP39 restoring as well, try it out.</div><div dir=3D=
"auto"><br></div><div dir=3D"auto">-Jon</div></div><br><div class=3D"gmail_=
quote"><div dir=3D"ltr">2018=E5=B9=B411=E6=9C=8816=E6=97=A5(=E9=87=91) 23:0=
4=E3=80=81Neill Miller =E3=81=95=E3=82=93=EF=BC=88<a href=3D"mailto:neillm@=
thecodefactory.org">neillm@thecodefactory.org</a>=EF=BC=89=E3=81=AE=E3=83=
=A1=E3=83=83=E3=82=BB=E3=83=BC=E3=82=B8:<br></div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">On Fri, Nov 09, 2018 at 02:17:30PM +0900, Jonathan Underwood via bitc=
oin-dev wrote:<br>
&gt; If more apps would implement to the word of the BIP39 spec, multiple<b=
r>
&gt; languages make sense, but since reality is no one follows the spec (/t=
he<br>
&gt; spec is way too open to interpretation) then expecting every app to lo=
ad<br>
&gt; every language is unreasonable.<br>
&gt; <br>
&gt; Electrum actually handles BIP39 recovery the way the BIP specifies. I =
can<br>
&gt; restore random strings if I want, and it warns me, and I can ignore it=
 if I<br>
&gt; wish.<br>
<br>
Electrum mnemonics are not based on BIP39, which is why it can do<br>
this.<br>
<br>
-Neill.<br>
<br>
</blockquote></div>

--000000000000e7d62d057ac8aa5f--