MIME-Version: 1.0
Sender: marek@palatinus.cz
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
Message-ID: <CAJna-HgfpyHX_0AHwt1Hkj0qhD_-xOcpxsZ9KXq=7CPgwse1hA@mail.gmail.com>
To: Pieter Wuille <pieter.wuille@gmail.com>
Content-Type: multipart/alternative; boundary=089e01182b8e4a6c5604f6882e88
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] New BIP32 structure
Precedence: list

--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 &quot;xprv&quot; does not contain bitcoins or that &quot;xpr=
v&quot; 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">&lt;<a href=3D"mailto:slush@centrum.cz" target=3D"_blank">slush@centr=
um.cz</a>&gt;</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--