public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Aaron Voisine <voisine@gmail.com>
To: Pavol Rusnak <stick@satoshilabs.com>,
	Sutch Sam <Sam@breadwallet.com>,
	 James MacWhyte <james@breadwallet.com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bip44 extension for P2SH/P2WSH/...
Date: Fri, 13 May 2016 14:42:19 -0700	[thread overview]
Message-ID: <CACq0ZD7BUaMnRgpx0ZxZu1Ok5weiJ9tbZnyFpXEHsTi==V_t_w@mail.gmail.com> (raw)
In-Reply-To: <57361577.7060207@satoshilabs.com>

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

That's a valid concern, but I don't see the conflict here. In order to
recover funds from a wallet conforming to BIPXX, you must have wallet
software that handles BIPXX. Simply making BIPXX backwards compatible with
previously created BIP44 or BIP43 purpose 0 wallets doesn't change this at
all.


Aaron Voisine
co-founder and CEO
breadwallet <http://breadwallet.com>

On Fri, May 13, 2016 at 10:57 AM, Pavol Rusnak <stick@satoshilabs.com>
wrote:

> On 13/05/16 18:59, Aaron Voisine wrote:
> > This scheme is independent of the number of accounts. It works with BIP44
> > as well as BIP43 purpose 0, or any other BIP43 purpose/layout. Instead of
> > overloading the account index to indicate the type of address, you use
> the
> > chain index, which is already being used to indicate what the specific
> > address chain is to be used for, i.e. receive vs change addresses.
>
> I see the advantage here. But there is a major problem here.
>
> We came up with BIP44 so a wallet can claim it is BIP44 compatible and
> you can be 100% sure that you can migrate accounts from one wallet
> implementation to another. This was not previously possible when a
> wallet claimed it is BIP32 compatible.
>
> Now we have a similar problem. When there is a BIP44 wallet, does it
> mean it supports segwit or not? For this reason I would like to see
> another BIPXX for segwit, so a wallet can claim it is BIP44, BIP44+BIPXX
> or BIPXX compatible and you'll know what other wallets are compatible
> with it.
>
> --
> Best Regards / S pozdravom,
>
> Pavol "stick" Rusnak
> SatoshiLabs.com
>

[-- Attachment #2: Type: text/html, Size: 2260 bytes --]

  reply	other threads:[~2016-05-13 21:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-13 13:16 [bitcoin-dev] Bip44 extension for P2SH/P2WSH/ Daniel Weigl
2016-05-13 15:00 ` Pavol Rusnak
2016-05-13 16:03   ` Aaron Voisine
2016-05-13 16:11     ` Pavol Rusnak
2016-05-13 16:59       ` Aaron Voisine
2016-05-13 17:57         ` Pavol Rusnak
2016-05-13 21:42           ` Aaron Voisine [this message]
2016-05-14  8:16             ` Jonas Schnelli
2016-05-14 12:26               ` Jochen Hoenicke
2016-05-14 14:07               ` Pavol Rusnak
2016-05-14 16:14                 ` Jonas Schnelli
2016-05-14 17:37                   ` Kenneth Heutmaker
2016-05-15  8:53                   ` Thomas Voegtlin
2016-05-15 10:04                   ` Pavol Rusnak
2016-05-15 12:08     ` Daniel Weigl
2016-05-15 17:36       ` Aaron Voisine
2016-05-14  7:00 ` Andreas Schildbach
2016-05-14 14:08   ` Pavol Rusnak
2016-05-14 17:09     ` Aaron Voisine
2016-05-14 12:15 ` Jochen Hoenicke

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='CACq0ZD7BUaMnRgpx0ZxZu1Ok5weiJ9tbZnyFpXEHsTi==V_t_w@mail.gmail.com' \
    --to=voisine@gmail.com \
    --cc=Sam@breadwallet.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=james@breadwallet.com \
    --cc=stick@satoshilabs.com \
    /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