From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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 ; 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: References: Date: Thu, 27 Mar 2014 10:57:51 -0500 Message-ID: From: Allen Piscitello To: Jeff Garzik 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 Subject: Re: [Bitcoin-development] New BIP32 structure X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 wrote: > On Thu, Mar 27, 2014 at 3:09 AM, Tamas Blummer > 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
Don'= t most of these coins have a magic number already assigned that is unique? = (0xD9B4BEF9=A0for Bitcoin,=A00x0709110B for Testn= et,=A0FBC0XB6DB 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?

<= /div>
-A= llen


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@bitso= fproof.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 a= nd
> cetral directory is not needed.

+1 good idea

--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. =A0 =A0 =A0h= ttps://bitpay.com/

---------------------------------------------------------------------------= ---
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--20cf301b69cdc9397f04f598a5b9--