public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: devrandom <c1.sf-bitcoin@niftybox.net>
To: Thy Shizzle <harro84@yahoo.com.au>
Cc: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Electrum 2.0 has been tagged
Date: Wed, 11 Mar 2015 19:26:45 -0700	[thread overview]
Message-ID: <5500F965.1010604@niftybox.net> (raw)
In-Reply-To: <372541993.4372759.1426123313134.JavaMail.yahoo@mail.yahoo.com>

On 2015-03-11 06:21 PM, Thy Shizzle wrote:
> Hmmmm I don't think it's fair to say that there has been a failure to
> standardise. From what I read earlier among the wallets, mostly it came
> down to if a version was noted and the date. Assuming no date is
> provided, it just means you are scanning the block chain from day 0 for
> transactions right? Hardly a big deal as you will still recover funds right?

Unfortunately there's more incompatibility than just the date issue:

* seed: some follow BIP39, and some roll their own
* HD structure: some follow BIP44, some BIP32 derivation, and some roll
their own

So actually very few wallets are seed-compatible, even ignoring the date
question.

> 
> Version right now is irrelevant as there is only one version of BIP39
> currently, probably this will change as 2048 iterations of HMACSHA512
> will likely need to be up scaled in the future, I thought about adding
> one extra word into the mnemonic to signify version, so if you have a 12
> word mnemonic then you have 12 words + 1 word version. Version 1 has no
> extra word, version 2 uses the first word on the list, version 3 uses
> the second word on the wordlist, so on and so forth. Least that's what I
> was thinking of doing if I ever had to record a version, won't effect
> anything because entropy increases in blocks of 3 words so one extra
> word can simply be thrown on the end.

That's a reasonable solution.

> 
> So in summary I feel that date can be handled by assuming day 0, and
> version is not an issue yet but may become one and probably it is a good
> idea to think about standardising a version into BIP39, I have
> provided a seed idea for discussion.
> 
> I don't think it is quite the doom and gloom I'm reading :)
> 
> 
> devrandom:
> "I'd like to offer that the best practice for the shared wallet use case
> should be multi-device multi-sig.  The mobile has a key, the desktop has
> a key and a third-party security oracle has a third key.  The oracle
> would have different security thresholds for countersigning the mobile.
> 
> This way you can have the same overall wallet on all devices, but
> different security profiles on different keys.
> 
> That said, I do agree that mnemonic phrases should be portable, and find
> it unfortunate that the ecosystem is failing to standardize on phrase
> handling."

-- 
devrandom / Miron



       reply	other threads:[~2015-03-12  2:26 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <372541993.4372759.1426123313134.JavaMail.yahoo@mail.yahoo.com>
2015-03-12  2:26 ` devrandom [this message]
2015-03-12  5:58 [Bitcoin-development] Electrum 2.0 has been tagged Thy Shizzle
  -- strict thread matches above, loose matches on Subject: below --
2015-03-12  5:12 Thy Shizzle
2015-03-12  5:25 ` Aaron Voisine
2015-03-12  4:21 Thy Shizzle
2015-03-12 11:51 ` Neill Miller
2015-03-12 12:59   ` Thy Shizzle
2015-03-12 16:39   ` devrandom
2015-03-12  2:38 Thy Shizzle
2015-03-12 10:43 ` Andreas Schildbach
     [not found] <1353069350.4360497.1426126034565.JavaMail.yahoo@mail.yahoo.com>
2015-03-12  2:16 ` Thy Shizzle
2015-03-12  3:59   ` Neill Miller
2015-03-01 15:23 Thomas Voegtlin
2015-03-02  7:09 ` Andreas Schildbach
2015-03-02 15:37 ` Mike Hearn
2015-03-02 17:11   ` Jim
2015-03-11 14:58   ` Thomas Voegtlin
2015-03-11 15:31     ` Andreas Schildbach
2015-03-12  8:56       ` Thomas Voegtlin
2015-03-11 17:14     ` Mike Hearn
2015-03-11 19:04       ` Jim
2015-03-11 19:24         ` Ricardo Filipe
2015-03-11 19:46           ` Gregory Maxwell
2015-03-11 22:57             ` Aaron Voisine
2015-03-11 23:22               ` Mike Hearn
2015-03-11 23:50                 ` devrandom
2015-03-11 23:54                   ` Mike Hearn
2015-03-12  0:11                   ` Gregory Maxwell
2015-03-12  2:41                     ` devrandom
2015-03-12  4:09                       ` Gregory Maxwell
2015-03-12 19:08                         ` Bryan Bishop
2015-03-12 10:30                     ` Andreas Schildbach
2015-03-12 10:28                   ` Andreas Schildbach
2015-03-18  2:06                     ` devrandom
2015-03-12 10:41         ` Andreas Schildbach
2015-03-12  3:43       ` slush
2015-03-12 16:47         ` Mike Hearn
2015-03-12 17:20           ` Gary Rowe
2015-03-12 17:42           ` Gary Rowe
2015-03-12 18:27           ` Natanael
2015-03-12 18:51             ` Andreas Schildbach
2015-03-12 19:14               ` Natanael

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=5500F965.1010604@niftybox.net \
    --to=c1.sf-bitcoin@niftybox.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=harro84@yahoo.com.au \
    /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