public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Neill Miller <neillm@thecodefactory•org>
To: Jonathan Underwood <junderwood@bitcoinbank•co.jp>
Cc: bitcoin-dev@lists•linuxfoundation.org, somber.night@protonmail•com
Subject: Re: [bitcoin-dev] BIP- & SLIP-0039 -- better multi-language support
Date: Fri, 16 Nov 2018 09:15:10 -0500	[thread overview]
Message-ID: <20181116141510.GB11584@boiler.chaos.net> (raw)
In-Reply-To: <CAMpN3mLRUD+cobNHtK=5dCL2hpGZJaR2TYzKb_643BC-wM5feQ@mail.gmail.com>

Ah, ok.  I've worked with the non-BIP39 Electrum mnemonics, which have
this behaviour, but haven't tried the BIP39 support within it.

Thanks,
-Neill.

On Fri, Nov 16, 2018 at 11:05:50PM +0900, Jonathan Underwood wrote:
> Nope.
> 
> This is how Electrum treats BIP39 restoring as well, try it out.
> 
> -Jon
> 
> 2018年11月16日(金) 23:04、Neill Miller さん(neillm@thecodefactory•org)のメッセージ:
> 
> > 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 (/the
> > > spec is way too open to interpretation) then expecting every app to load
> > > every language is unreasonable.
> > >
> > > Electrum actually handles BIP39 recovery the way the BIP specifies. I can
> > > 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.
> >
> >


  reply	other threads:[~2018-11-16 14:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 10:37 SomberNight
2018-11-09  5:17 ` Jonathan Underwood
2018-11-16 14:03   ` Neill Miller
2018-11-16 14:05     ` Jonathan Underwood
2018-11-16 14:15       ` Neill Miller [this message]
     [not found] <mailman.2299.1542895684.19477.bitcoin-dev@lists.linuxfoundation.org>
2018-11-22 17:25 ` Weiji Guo
     [not found] <CABsxsG27bJN0vGRJOP3=zriPvkL+G8n3t2nd6Y8L6KwW4ePdeg@mail.gmail.com>
2018-11-19 19:54 ` Steven Hatzakis
2018-11-20  1:51   ` Natanael
     [not found] <mailman.1087.1541036387.10264.bitcoin-dev@lists.linuxfoundation.org>
2018-11-06 16:16 ` Weiji Guo

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=20181116141510.GB11584@boiler.chaos.net \
    --to=neillm@thecodefactory$(echo .)org \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=junderwood@bitcoinbank$(echo .)co.jp \
    --cc=somber.night@protonmail$(echo .)com \
    /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