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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <marek@palatinus.cz>) id 1WXWKE-0000Kd-Cm
for bitcoin-development@lists.sourceforge.net;
Tue, 08 Apr 2014 13:44:30 +0000
X-ACL-Warn:
Received: from mail-vc0-f171.google.com ([209.85.220.171])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WXWK9-0004JM-0W
for bitcoin-development@lists.sourceforge.net;
Tue, 08 Apr 2014 13:44:30 +0000
Received: by mail-vc0-f171.google.com with SMTP id lg15so760016vcb.16
for <bitcoin-development@lists.sourceforge.net>;
Tue, 08 Apr 2014 06:44:19 -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:to:cc:content-type;
bh=8lr9iTB6dyK9hlfAyXP4sRKdV8SGIOuEdRDWNnRsXcU=;
b=RIkSExn/7qwVcOobO3X0JdkbTVGiOx2I8yTpiN5tQo6kcB5ExK+k8bdTaJqdqe1a12
yPcvaMv9Bu9OE0Jatq7/D1XKkFN/XV+r0elQIZ7ay1xZ2iK+7kEXybR2zO7fRNxx7hq6
Hap5TlGnQcHotONwNoyYqVC1+kD9q3OtEPAh+9UrYmUyZ/80TTZk+CdRatejv9PcGDho
KxdSQPnK42JTWyRxk6qhj5JMdF34WxT9Qjz0DIfCa+jw2xxGbPrQycMvMOjDZiyZMq7y
E9ZCVWPq6nz/74i4B4Yr8amH50bKti8QIScacDmZ8dUH7vneKiy1niylchkktXz9d1c/
A2gQ==
X-Gm-Message-State: ALoCoQkplwhBvycC1f3fezNeqUoq+YcYLVxRP5J3YuXWqiI/YWUteVAVThIDwYgowW5YypCfuUz7
X-Received: by 10.58.90.99 with SMTP id bv3mr166410veb.34.1396964659455; Tue,
08 Apr 2014 06:44:19 -0700 (PDT)
MIME-Version: 1.0
Sender: marek@palatinus.cz
Received: by 10.58.234.100 with HTTP; Tue, 8 Apr 2014 06:43:49 -0700 (PDT)
In-Reply-To: <CAJna-HiN_1KQmpDJFFX6mGvM63RC0xwXxvfuorpihnzYf4=fsQ@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>
<CAJna-HirtsGLfAhfUf9dAYEGWo6g=o=eAU187c2pdW8vDFGkPw@mail.gmail.com>
<CAPg+sBg8wDH9yTUoyhRbuzVtbD8hGxya8tOnV4pMToHy3gLrzw@mail.gmail.com>
<CAJna-HiN_1KQmpDJFFX6mGvM63RC0xwXxvfuorpihnzYf4=fsQ@mail.gmail.com>
From: slush <slush@centrum.cz>
Date: Tue, 8 Apr 2014 15:43:49 +0200
X-Google-Sender-Auth: G_OAUvVIyNuz10vA-TMhws12fIc
Message-ID: <CAJna-HgfpyHX_0AHwt1Hkj0qhD_-xOcpxsZ9KXq=7CPgwse1hA@mail.gmail.com>
To: Pieter Wuille <pieter.wuille@gmail.com>
Content-Type: multipart/alternative; boundary=089e01182b8e4a6c5604f6882e88
X-Spam-Score: 1.0 (+)
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.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1WXWK9-0004JM-0W
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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 13:44:30 -0000
--089e01182b8e4a6c5604f6882e88
Content-Type: text/plain; charset=ISO-8859-1
tl;dr;
It is dangerous to expect that other seed than "xprv" does not contain
bitcoins or that "xprv" contains only bitcoins, because technically are
both situations possible. It is still safer to do the lookup; the magic
itself is ambiguous.
Marek
On Tue, Apr 8, 2014 at 3:40 PM, slush <slush@centrum.cz> wrote:
>
> Serialization magic of bip32 seed is in my opinion completely unnecessary.
> Most of software does not care about it anyway; You can use xprv/xpub pair
> for main net, testnet, litecoin, dogecoin, whatevercoin.
>
> Instead using the same seed (xprv) and then separate the chains *inside*
> the bip32 path seems more useful to me.
>
> Marek
>
--089e01182b8e4a6c5604f6882e88
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">tl;dr;<div><br></div><div>It is dangerous to expect that o=
ther seed than "xprv" does not contain bitcoins or that "xpr=
v" contains only bitcoins, because technically are both situations pos=
sible. It is still safer to do the lookup; the magic itself is ambiguous.<b=
r>
<div class=3D"gmail_extra"><br>Marek</div><div class=3D"gmail_extra"><br><d=
iv class=3D"gmail_quote">On Tue, Apr 8, 2014 at 3:40 PM, slush <span dir=3D=
"ltr"><<a href=3D"mailto:slush@centrum.cz" target=3D"_blank">slush@centr=
um.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"><div class=3D"gmail_extra">=
<div class=3D"gmail_quote"><div class=3D""><div><br></div></div><div>Serial=
ization magic of bip32 seed is in my opinion completely unnecessary. Most o=
f software does not care about it anyway; You can use xprv/xpub pair for ma=
in net, testnet, litecoin, dogecoin, whatevercoin.</div>
<div><br></div><div>Instead using the same seed (xprv) and then separate th=
e chains *inside* the bip32 path seems more useful to me.</div><div><br></d=
iv><div>Marek=A0</div></div></div></div>
</blockquote></div><br></div></div></div>
--089e01182b8e4a6c5604f6882e88--
|
