Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.160.172 as permitted sender)
	client-ip=209.85.160.172;
	envelope-from=allen.piscitello@gmail.com;
	helo=mail-yk0-f172.google.com; 
MIME-Version: 1.0
In-Reply-To: <53344C7C.7020407@gk2.sk>
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>
	<53344C7C.7020407@gk2.sk>
Date: Thu, 27 Mar 2014 11:13:46 -0500
Message-ID: <CAJfRnm79ho7anNZCPmMgDOaYBZkS0jez8Xcrh7GJHRJFheJB8Q@mail.gmail.com>
From: Allen Piscitello <allen.piscitello@gmail.com>
To: Pavol Rusnak <stick@gk2.sk>
Content-Type: multipart/alternative; boundary=20cf301b69cdb47d3104f598de28
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] New BIP32 structure
Precedence: list

--20cf301b69cdb47d3104f598de28
Content-Type: text/plain; charset=ISO-8859-1

The idea was to use the magic number as the source for cointype.  If it's
too big, as Tamas showed, perhaps a hash of it, and for coins without a
magic number, a hash of their name (or some unique identifier).

That being said, I agree with Andreas that something that is 90%
inter-operable seems very dangerous and will give people false expectations
when they miss the corner cases.  If the structure isn't going to be shared
completely and have all support shared, having it completely incompatible
along with a mechanism for converting part of it to another wallet seems
superior.  The worst types of losses will occur when someone tests out
something with a limited use case, sees that it appears to work, makes
dangerous assumptions, then gets burned when it's too late.

-Allen


On Thu, Mar 27, 2014 at 11:06 AM, Pavol Rusnak <stick@gk2.sk> wrote:

> On 03/27/2014 04:57 PM, Allen Piscitello wrote:
> > Don't most of these coins have a magic number already assigned that is
> > unique? (0xD9B4BEF9 for Bitcoin, 0x0709110B for Testnet, FBC0XB6DB for
> > Litecoin, etc...).  This seems like a good candidate for identifying
> coins,
> > and also supports Testnet cases well.  Maybe there are some alts without
> > such a magic number that might prevent that?
>
> That magic number is something I find very unfortunate and superflous in
> BIP-32 design. Its only purpose is to distinguish BIP-32 trees for
> various altcoins, but it doesn't make sense at all once you start
> storing various altcoins in the same tree using the proposed
> /m/cointype/reserved'/account'/change/n scheme.
>
> I would love to see that removed from BIP-32 and use always
> 0x0488B21E/0x0488ADE4 (xpub/xpriv), but that is for different discussion
> I guess.
>
> --
> Best Regards / S pozdravom,
>
> Pavol Rusnak <stick@gk2.sk>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

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

<div dir=3D"ltr">The idea was to use the magic number as the source for coi=
ntype. =A0If it&#39;s too big, as Tamas showed, perhaps a hash of it, and f=
or coins without a magic number, a hash of their name (or some unique ident=
ifier).<div>
<br></div><div>That being said, I agree with Andreas that something that is=
 90% inter-operable seems very dangerous and will give people false expecta=
tions when they miss the corner cases. =A0If the structure isn&#39;t going =
to be shared completely and have all support shared, having it completely i=
ncompatible along with a mechanism for converting part of it to another wal=
let seems superior. =A0The worst types of losses will occur when someone te=
sts out something with a limited use case, sees that it appears to work, ma=
kes dangerous assumptions, then gets burned when it&#39;s too late.</div>
<div><br></div><div>-Allen</div></div><div class=3D"gmail_extra"><br><br><d=
iv class=3D"gmail_quote">On Thu, Mar 27, 2014 at 11:06 AM, Pavol Rusnak <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:stick@gk2.sk" target=3D"_blank">stick@=
gk2.sk</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 03/27/2014 04:57 PM, Alle=
n Piscitello wrote:<br>
&gt; Don&#39;t most of these coins have a magic number already assigned tha=
t is<br>
&gt; unique? (0xD9B4BEF9 for Bitcoin, 0x0709110B for Testnet, FBC0XB6DB for=
<br>
&gt; Litecoin, etc...). =A0This seems like a good candidate for identifying=
 coins,<br>
&gt; and also supports Testnet cases well. =A0Maybe there are some alts wit=
hout<br>
&gt; such a magic number that might prevent that?<br>
<br>
</div>That magic number is something I find very unfortunate and superflous=
 in<br>
BIP-32 design. Its only purpose is to distinguish BIP-32 trees for<br>
various altcoins, but it doesn&#39;t make sense at all once you start<br>
storing various altcoins in the same tree using the proposed<br>
/m/cointype/reserved&#39;/account&#39;/change/n scheme.<br>
<br>
I would love to see that removed from BIP-32 and use always<br>
0x0488B21E/0x0488ADE4 (xpub/xpriv), but that is for different discussion<br=
>
I guess.<br>
<div class=3D"im HOEnZb"><br>
--<br>
Best Regards / S pozdravom,<br>
<br>
Pavol Rusnak &lt;<a href=3D"mailto:stick@gk2.sk">stick@gk2.sk</a>&gt;<br>
<br>
</div><div class=3D"HOEnZb"><div class=3D"h5">-----------------------------=
-------------------------------------------------<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>

--20cf301b69cdb47d3104f598de28--