<oembed><type>rich</type><version>1.0</version><author_name>npub1ad7209g90jnu400x74quws0xv8gpxs2fxnjexnpwqnrxwa39exdq5gl2p6</author_name><author_url>https://nostr.ae/npub1ad7209g90jnu400x74quws0xv8gpxs2fxnjexnpwqnrxwa39exdq5gl2p6</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2014-03-28&#xA;📝 Original message:I agree that &#39;version&#39; field of bip32 is not necessary and xpriv/xpub&#xA;should be enough for all cases; there&#39;s actually no need to use different&#xA;BIP32 roots for different altcoins.&#xA;&#xA;I&#39;m happily using one xpub for Bitcoin/Testnet/Litecoin at once, and by&#xA;having the &#34;cointype&#34; distinction in the bip32 path itself, I&#39;m sure that I&#xA;don&#39;t reuse the same pubkey across blockchains which may be a privacy issue&#xA;otherwise.&#xA;&#xA;Marek&#xA;&#xA;&#xA;On Thu, Mar 27, 2014 at 5:28 PM, Pieter Wuille &lt;pieter.wuille at gmail.com&gt;wrote:&#xA;&#xA;&gt; On Thu, Mar 27, 2014 at 5:21 PM, Pavol Rusnak &lt;stick at gk2.sk&gt; wrote:&#xA;&gt; &gt; Cointype in path is for separation purposes, not for identification.&#xA;&gt;&#xA;&gt; I don&#39;t understand what that gains you.&#xA;&gt;&#xA;&gt; --&#xA;&gt; Pieter&#xA;&gt;&#xA;&gt;&#xA;&gt; ------------------------------------------------------------------------------&#xA;&gt; _______________________________________________&#xA;&gt; Bitcoin-development mailing list&#xA;&gt; Bitcoin-development at lists.sourceforge.net&#xA;&gt; https://lists.sourceforge.net/lists/listinfo/bitcoin-development&#xA;&gt;&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140328/8b081833/attachment.html&gt;</html></oembed>