1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
|
Return-Path: <voisine@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id EF0F125A
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 13 May 2016 21:42:20 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-yw0-f177.google.com (mail-yw0-f177.google.com
[209.85.161.177])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 503FC229
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 13 May 2016 21:42:20 +0000 (UTC)
Received: by mail-yw0-f177.google.com with SMTP id o66so129798739ywc.3
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 13 May 2016 14:42:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc; bh=jSLyG+eRN/AHVfSxvcmA+yiei5CVOtjNz/vWOEeqybg=;
b=bJMn8anFQQR9X6bfMRcVoMQ+JSSv0StXNitOL44NKpGZ+aujTNZ+A8zxlWe4G2izjL
H+b5HGqjhJF5eA/y30HPv35DIi6XTzYD2B4pWYYMcgkP9Vs5HjcFVba0zUNrBkOX3188
nKFmjLczdaWD3IkSEEgD8f+3TsBjfF2ly2wQXvl0sYN4QbD5idiDv0PEdyIjXH5SIxSv
sjpCt7jxfs3jakEWzXWAyyF8L93q01qUrArUsBEYHXQ/QNgfbMzH5jHJUdIuque/c3mQ
Eyj+fqKuAdhpV7msrl2xBgM7EHZx2BMnm/VUADEqHijXDObS4n9uHk1fxpjE0SDiLkny
wLcg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc;
bh=jSLyG+eRN/AHVfSxvcmA+yiei5CVOtjNz/vWOEeqybg=;
b=BHRWg4hAUKfXA8ChEQOZlz8fXtogMfPhN3/iY+5a0o0v4bXDe9MIOoytn1l2eCjjQv
TI85h5HyP1UPmD8cfZJFV/ISmchcZw8AOksIW+EpU/oPMOtOvwZXjlwACjlEXWzoqwZn
qKzd/8idp71R1h5RsOnTIDuYZOmLMhojaqb3TyrUl+Re1WbqLUT0VNzCnVtq4kkRHGVp
qdB3C448WlMMQPsrfmE65TB6D+d0fVJ+dQfle3sbkFHf1Hw/DzocofIz50T6Cai2KZnl
ivx0ExqabMLtGIlLKIv87A6kYxTs0nrDIJemys6f0ggFVxLhmzkP0SFIN5S8UryVJduw
J1aw==
X-Gm-Message-State: AOPr4FVxYPUBiZ4c/hvbODysKPvCCN0Wpliw8yIGvpQ3gW/IHFnIEx8/E9+pBdwT+fW24MV5SgowKAoBMCiPJw==
MIME-Version: 1.0
X-Received: by 10.37.48.2 with SMTP id w2mr8595132ybw.86.1463175739453; Fri,
13 May 2016 14:42:19 -0700 (PDT)
Received: by 10.13.233.2 with HTTP; Fri, 13 May 2016 14:42:19 -0700 (PDT)
In-Reply-To: <57361577.7060207@satoshilabs.com>
References: <5735D3A4.7090608@mycelium.com> <5735EC17.5040901@satoshilabs.com>
<CACq0ZD4BvvCryYmO-J9Rof-ogQJ1wNLgmUEU596nuTH=-U8Hag@mail.gmail.com>
<5735FC99.5090001@satoshilabs.com>
<CACq0ZD7mLCaoGpcVEp7NfW=6nsEA39tZp+G8oeySygMEyhuwQA@mail.gmail.com>
<57361577.7060207@satoshilabs.com>
Date: Fri, 13 May 2016 14:42:19 -0700
Message-ID: <CACq0ZD7BUaMnRgpx0ZxZu1Ok5weiJ9tbZnyFpXEHsTi==V_t_w@mail.gmail.com>
From: Aaron Voisine <voisine@gmail.com>
To: Pavol Rusnak <stick@satoshilabs.com>, Sutch Sam <Sam@breadwallet.com>,
James MacWhyte <james@breadwallet.com>
Content-Type: multipart/alternative; boundary=94eb2c03448831ba290532c026ae
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bip44 extension for P2SH/P2WSH/...
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 13 May 2016 21:42:21 -0000
--94eb2c03448831ba290532c026ae
Content-Type: text/plain; charset=UTF-8
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
>
--94eb2c03448831ba290532c026ae
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">That's a valid concern, but I don't see the confli=
ct here. In order to recover funds from a wallet conforming to BIPXX, you m=
ust have wallet software that handles BIPXX. Simply making BIPXX backwards =
compatible with previously created BIP44 or BIP43 purpose 0 wallets doesn&#=
39;t change this at all.</div><div class=3D"gmail_extra"><br clear=3D"all">=
<div><div class=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr">=
<div><div dir=3D"ltr"><div><br>Aaron Voisine</div><div>co-founder and CEO<b=
r><a href=3D"http://breadwallet.com" target=3D"_blank">breadwallet</a></div=
></div></div></div></div></div></div></div>
<br><div class=3D"gmail_quote">On Fri, May 13, 2016 at 10:57 AM, Pavol Rusn=
ak <span dir=3D"ltr"><<a href=3D"mailto:stick@satoshilabs.com" target=3D=
"_blank">stick@satoshilabs.com</a>></span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><span class=3D"">On 13/05/16 18:59, Aaron Voisine wrote:<br>
> This scheme is independent of the number of accounts. It works with BI=
P44<br>
> as well as BIP43 purpose 0, or any other BIP43 purpose/layout. Instead=
of<br>
> overloading the account index to indicate the type of address, you use=
the<br>
> chain index, which is already being used to indicate what the specific=
<br>
> address chain is to be used for, i.e. receive vs change addresses.<br>
<br>
</span>I see the advantage here. But there is a major problem here.<br>
<br>
We came up with BIP44 so a wallet can claim it is BIP44 compatible and<br>
you can be 100% sure that you can migrate accounts from one wallet<br>
implementation to another. This was not previously possible when a<br>
wallet claimed it is BIP32 compatible.<br>
<br>
Now we have a similar problem. When there is a BIP44 wallet, does it<br>
mean it supports segwit or not? For this reason I would like to see<br>
another BIPXX for segwit, so a wallet can claim it is BIP44, BIP44+BIPXX<br=
>
or BIPXX compatible and you'll know what other wallets are compatible<b=
r>
with it.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
--<br>
Best Regards / S pozdravom,<br>
<br>
Pavol "stick" Rusnak<br>
SatoshiLabs.com<br>
</div></div></blockquote></div><br></div>
--94eb2c03448831ba290532c026ae--
|
