Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <allen.piscitello@gmail.com>) id 1WTCgo-0005Ns-KI for bitcoin-development@lists.sourceforge.net; Thu, 27 Mar 2014 15:57:58 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.49 as permitted sender) client-ip=209.85.213.49; envelope-from=allen.piscitello@gmail.com; helo=mail-yh0-f49.google.com; Received: from mail-yh0-f49.google.com ([209.85.213.49]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WTCgn-00073i-Jg for bitcoin-development@lists.sourceforge.net; Thu, 27 Mar 2014 15:57:58 +0000 Received: by mail-yh0-f49.google.com with SMTP id z6so3779950yhz.36 for <bitcoin-development@lists.sourceforge.net>; Thu, 27 Mar 2014 08:57:52 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.236.100.226 with SMTP id z62mr2417033yhf.111.1395935872103; Thu, 27 Mar 2014 08:57:52 -0700 (PDT) Received: by 10.170.88.10 with HTTP; Thu, 27 Mar 2014 08:57:51 -0700 (PDT) In-Reply-To: <CAJHLa0PPAsBLgsy0vgPpUp=UzeR_fWUEzFb5+xtmODEk4MGPVQ@mail.gmail.com> References: <CANEZrP2hbBVGqytmXR1rAcVama4ONnR586Se-Ch=dsxOzy2O4w@mail.gmail.com> <F2C8C044-EF92-4CCE-9235-28CA7FCE3526@bitsofproof.com> <CAJHLa0PPAsBLgsy0vgPpUp=UzeR_fWUEzFb5+xtmODEk4MGPVQ@mail.gmail.com> Date: Thu, 27 Mar 2014 10:57:51 -0500 Message-ID: <CAJfRnm7V6fgcj=TMfa2ZTYWOKtE5aoUT1xnVtKUSyriB=6cagQ@mail.gmail.com> From: Allen Piscitello <allen.piscitello@gmail.com> To: Jeff Garzik <jgarzik@bitpay.com> Content-Type: multipart/alternative; boundary=20cf301b69cdc9397f04f598a5b9 X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (allen.piscitello[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1WTCgn-00073i-Jg 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: Thu, 27 Mar 2014 15:57:58 -0000 --20cf301b69cdc9397f04f598a5b9 Content-Type: text/plain; charset=ISO-8859-1 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? -Allen On Thu, Mar 27, 2014 at 10:43 AM, Jeff Garzik <jgarzik@bitpay.com> wrote: > On Thu, Mar 27, 2014 at 3:09 AM, Tamas Blummer <tamas@bitsofproof.com> > wrote: > > A notable suggestion was to instead of building a directory of magic > numbers > > (like 0 for Bitcoin, 1 for Litecoin etc) use a hash of the word > "Bitcoin", > > "Litecoin", "Dogecoin", so collosion is unlikely and > > cetral directory is not needed. > > +1 good idea > > -- > Jeff Garzik > Bitcoin core developer and open source evangelist > BitPay, Inc. https://bitpay.com/ > > > ------------------------------------------------------------------------------ > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > --20cf301b69cdc9397f04f598a5b9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><span style=3D"background-color:rgb(255,255,255)">Don'= t most of these coins have a magic number already assigned that is unique? = (<span style=3D"color:rgb(0,0,0);font-family:sans-serif;font-size:13px;line= -height:19.200000762939453px">0xD9B4BEF9</span><span style=3D"color:rgb(0,0= ,0);font-family:sans-serif;font-size:13px;line-height:19.200000762939453px"= >=A0for Bitcoin,=A0</span><span style=3D"color:rgb(0,0,0);font-family:sans-= serif;font-size:13px;line-height:19.200000762939453px">0x0709110B for Testn= et,=A0</span><span style=3D"color:rgb(0,0,0);font-family:sans-serif;font-si= ze:13px;line-height:19.200000762939453px">FBC0XB6DB for Litecoin, etc...). = =A0This seems like a good candidate for identifying coins, and also support= s Testnet cases well. =A0Maybe there are some alts without such a magic num= ber that might prevent that?</span></span><div> <span style=3D"color:rgb(0,0,0);font-family:sans-serif;font-size:13px;line-= height:19.200000762939453px;background-color:rgb(255,255,255)"><br></span><= /div><div><span style=3D"color:rgb(0,0,0);font-family:sans-serif;font-size:= 13px;line-height:19.200000762939453px;background-color:rgb(255,255,255)">-A= llen</span></div> </div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu,= Mar 27, 2014 at 10:43 AM, Jeff Garzik <span dir=3D"ltr"><<a href=3D"mai= lto:jgarzik@bitpay.com" target=3D"_blank">jgarzik@bitpay.com</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 class=3D"">On Thu, Mar 27, 2014 at 3:09= AM, Tamas Blummer <<a href=3D"mailto:tamas@bitsofproof.com">tamas@bitso= fproof.com</a>> wrote:<br> </div><div class=3D"">> A notable suggestion was to instead of building = a directory of magic numbers<br> > (like 0 for Bitcoin, 1 for Litecoin etc) use a hash of the word "= Bitcoin",<br> > "Litecoin", "Dogecoin", so collosion is unlikely a= nd<br> > cetral directory is not needed.<br> <br> </div>+1 good idea<br> <span class=3D"HOEnZb"><font color=3D"#888888"><br> --<br> Jeff Garzik<br> Bitcoin core developer and open source evangelist<br> BitPay, Inc. =A0 =A0 =A0<a href=3D"https://bitpay.com/" target=3D"_blank">h= ttps://bitpay.com/</a><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> --20cf301b69cdc9397f04f598a5b9--