MIME-Version: 1.0
Sender: marek@palatinus.cz
In-Reply-To: <CAPg+sBhbx5vy_hewAkFPaiXHzSMNH0qLhEYGjPmQMjR5StP-tw@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>
From: slush <slush@centrum.cz>
Date: Fri, 28 Mar 2014 15:59:47 +0100
Message-ID: <CAJna-Hi0JnrF2_rUx0rGkdnsuCoaD01e3Gobpn+QqbL=D1Uivg@mail.gmail.com>
To: Pieter Wuille <pieter.wuille@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c2d3b6be580204f5abf5eb
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] New BIP32 structure
Precedence: list

--001a11c2d3b6be580204f5abf5eb
Content-Type: text/plain; charset=ISO-8859-1

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
>

--001a11c2d3b6be580204f5abf5eb
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I agree that &#39;version&#39; field of bip32 is not neces=
sary and xpriv/xpub should be enough for all cases; there&#39;s actually no=
 need to use different BIP32 roots for different altcoins.<div><br></div><d=
iv>

I&#39;m happily using one xpub for Bitcoin/Testnet/Litecoin at once, and by=
 having the &quot;cointype&quot; distinction in the bip32 path itself, I=
9;m sure that I don&#39;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"gmail_extra"><br><br><di=
v class=3D"gmail_quote">On Thu, Mar 27, 2014 at 5:28 PM, Pieter Wuille <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:pieter.wuille@gmail.com" target=3D"_bla=
nk">pieter.wuille@gmail.com</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 class=3D"">On Thu, Mar 27, 2014 at 5:21=
 PM, Pavol Rusnak &lt;<a href=3D"mailto:stick@gk2.sk">stick@gk2.sk</a>&gt; =
wrote:<br>


&gt; Cointype in path is for separation purposes, not for identification.<b=
r>
<br>
</div>I don&#39;t understand what that gains you.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
Pieter<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
---------------------------------------------------------------------------=
---<br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@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>

--001a11c2d3b6be580204f5abf5eb--