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
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <marek@palatinus.cz>) id 1WXVNn-0006CK-TR
for bitcoin-development@lists.sourceforge.net;
Tue, 08 Apr 2014 12:44:07 +0000
X-ACL-Warn:
Received: from mail-ve0-f174.google.com ([209.85.128.174])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WXVNm-00033A-Kt
for bitcoin-development@lists.sourceforge.net;
Tue, 08 Apr 2014 12:44:07 +0000
Received: by mail-ve0-f174.google.com with SMTP id oz11so683747veb.5
for <bitcoin-development@lists.sourceforge.net>;
Tue, 08 Apr 2014 05:44:01 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:sender:in-reply-to:references:from
:date:message-id:subject:cc:content-type;
bh=z2JG9eC7W6yoWuo91/Q0ivRGiZ4PR6uMEMLRX8oQCx0=;
b=ReD8Pm0hEFuXcI1Y+usTHJumSFO8SL404jsNcLNroqdBsoCl3oSaJPxIfXLMPoO2js
AeLLdKv+Bhb+jvYmuPIzmyjL43GKHjDzj+j7LNu1E0At66B9aj801yRrhLAAx9VQQzAk
kTaK4+zYGzV1/mF2jizqpU5n+uarIo8eoaEW8UiFFbSbYub6tw5f1X6VS9Off2HSeBUy
hJNWZcAqv8adJZU5bgnaP6hAcYc5QxVhUkqDknPTgSa9fcKTwdpYDXahZXX4nUUkf5Ys
NUeIFRU1K730WGrVH81ekKIGGjtITXyvdDmNQxUMU38bCDR35ijIGm3jw53yMumHaNbt
5HAA==
X-Gm-Message-State: ALoCoQk6n2/shp3WbaE4MZ84Mfw3yvS+H9S1xY6ItcCgaUc8zFSvgQn+GSEA5oaMFOoT8yZdasBh
X-Received: by 10.52.119.197 with SMTP id kw5mr2576005vdb.5.1396961040929;
Tue, 08 Apr 2014 05:44:00 -0700 (PDT)
MIME-Version: 1.0
Sender: marek@palatinus.cz
Received: by 10.58.234.100 with HTTP; Tue, 8 Apr 2014 05:43:30 -0700 (PDT)
In-Reply-To: <CAJna-Hi0JnrF2_rUx0rGkdnsuCoaD01e3Gobpn+QqbL=D1Uivg@mail.gmail.com>
References: <CANEZrP2hbBVGqytmXR1rAcVama4ONnR586Se-Ch=dsxOzy2O4w@mail.gmail.com>
<F2C8C044-EF92-4CCE-9235-28CA7FCE3526@bitsofproof.com>
<CAJHLa0PPAsBLgsy0vgPpUp=UzeR_fWUEzFb5+xtmODEk4MGPVQ@mail.gmail.com>
<CAJfRnm7V6fgcj=TMfa2ZTYWOKtE5aoUT1xnVtKUSyriB=6cagQ@mail.gmail.com>
<CAPg+sBjwf1TcK1CGKVKFzYbV-78j8t-pav7=PEgG7Yqi6-yE7A@mail.gmail.com>
<53344FF8.7030204@gk2.sk>
<CAPg+sBhbx5vy_hewAkFPaiXHzSMNH0qLhEYGjPmQMjR5StP-tw@mail.gmail.com>
<CAJna-Hi0JnrF2_rUx0rGkdnsuCoaD01e3Gobpn+QqbL=D1Uivg@mail.gmail.com>
From: slush <slush@centrum.cz>
Date: Tue, 8 Apr 2014 14:43:30 +0200
X-Google-Sender-Auth: RaRKMznteZOqVZjphwUwmlLy4Ps
Message-ID: <CAJna-HirtsGLfAhfUf9dAYEGWo6g=o=eAU187c2pdW8vDFGkPw@mail.gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=089e013a0f8a9c286704f687564a
X-Spam-Score: 2.2 (++)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(slush[at]centrum.cz)
1.2 MISSING_HEADERS Missing To: header
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1WXVNm-00033A-Kt
Subject: Re: [Bitcoin-development] New BIP32 structure
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 12:44:08 -0000
--089e013a0f8a9c286704f687564a
Content-Type: text/plain; charset=ISO-8859-1
After some off-list discussion about details with wallet developers, it
seems that structure
m/<cointype>'/<account>'/<change>/<n>
fulfill requirements of all wallet developers around, including myTrezor,
Electrum, Multibit, Wallet32 and other software is willing to adapt once
anything will be standardized (i.e. they don't care).
Because I think that everybody told their comments to the topic already and
because it seems that there's quite wide agreement on that, I would like to
close the discussion and finally implement these paths into our software.
Cheers,
Marek
On Fri, Mar 28, 2014 at 3:59 PM, slush <slush@centrum.cz> wrote:
> I agree that 'version' field of bip32 is not necessary and xpriv/xpub
> should be enough for all cases; there's actually no need to use different
> BIP32 roots for different altcoins.
>
> I'm happily using one xpub for Bitcoin/Testnet/Litecoin at once, and by
> having the "cointype" distinction in the bip32 path itself, I'm sure that I
> don't reuse the same pubkey across blockchains which may be a privacy issue
> otherwise.
>
> Marek
>
>
> On Thu, Mar 27, 2014 at 5:28 PM, Pieter Wuille <pieter.wuille@gmail.com>wrote:
>
>> On Thu, Mar 27, 2014 at 5:21 PM, Pavol Rusnak <stick@gk2.sk> wrote:
>> > Cointype in path is for separation purposes, not for identification.
>>
>> I don't understand what that gains you.
>>
>> --
>> Pieter
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>
>
--089e013a0f8a9c286704f687564a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">After some off-list discussion about details with wallet d=
evelopers, it seems that structure<div><br></div><div>m/<cointype>=
9;/<account>'/<change>/<n>=A0</div><div><br></div><di=
v>
fulfill requirements of all wallet developers around, including myTrezor, E=
lectrum, Multibit, Wallet32 and other software is willing to adapt once any=
thing will be standardized (i.e. they don't care).</div><div><br></div>
<div>Because I think that everybody told their comments to the topic alread=
y and because it seems that there's quite wide agreement on that, I wou=
ld like to close the discussion and finally implement these paths into our =
software.</div>
<div><br></div><div>Cheers,</div><div>Marek</div></div><div class=3D"gmail_=
extra"><br><br><div class=3D"gmail_quote">On Fri, Mar 28, 2014 at 3:59 PM, =
slush <span dir=3D"ltr"><<a href=3D"mailto:slush@centrum.cz" target=3D"_=
blank">slush@centrum.cz</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">I agree that 'version&#=
39; field of bip32 is not necessary and xpriv/xpub should be enough for all=
cases; there's actually no need to use different BIP32 roots for diffe=
rent altcoins.<div>
<br></div><div>
I'm happily using one xpub for Bitcoin/Testnet/Litecoin at once, and by=
having the "cointype" distinction in the bip32 path itself, I=
9;m sure that I don't reuse the same pubkey across blockchains which ma=
y be a privacy issue otherwise.</div>
<div><br></div><div>Marek</div></div><div class=3D"HOEnZb"><div class=3D"h5=
"><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu, Mar=
27, 2014 at 5:28 PM, Pieter Wuille <span dir=3D"ltr"><<a href=3D"mailto=
:pieter.wuille@gmail.com" target=3D"_blank">pieter.wuille@gmail.com</a>>=
</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div>On Thu, Mar 27, 2014 at 5:21 PM, Pavol =
Rusnak <<a href=3D"mailto:stick@gk2.sk" target=3D"_blank">stick@gk2.sk</=
a>> wrote:<br>
> Cointype in path is for separation purposes, not for identification.<b=
r>
<br>
</div>I don't understand what that gains you.<br>
<span><font color=3D"#888888"><br>
--<br>
Pieter<br>
</font></span><div><div><br>
---------------------------------------------------------------------------=
---<br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net" target=3D"_bla=
nk">Bitcoin-development@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
--089e013a0f8a9c286704f687564a--
|
