Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WTCSt-00057O-Pv for bitcoin-development@lists.sourceforge.net; Thu, 27 Mar 2014 15:43:35 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com designates 209.85.213.48 as permitted sender) client-ip=209.85.213.48; envelope-from=jgarzik@bitpay.com; helo=mail-yh0-f48.google.com; Received: from mail-yh0-f48.google.com ([209.85.213.48]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WTCSs-0006TN-Sv for bitcoin-development@lists.sourceforge.net; Thu, 27 Mar 2014 15:43:35 +0000 Received: by mail-yh0-f48.google.com with SMTP id z6so3713893yhz.35 for ; Thu, 27 Mar 2014 08:43:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=5WlqYmRahb557jzpQVcFpyEN07WPXP+U93dRUuE6KPo=; b=WzXyNCXfTxJbFjLTOC9wiRTlXH5zROEkDltGS+yDEkCbQLx+uDJjx7Vw7dEO46ZFSu UQvcnLa8wz2Qwo2z6qHuZA5NUzFM+6nSLscrMB2wZ2awcx42a3TatgIflv9LaP7RVTeT fdAlhlYuL/2PqG5MwfFf4jhXVCXSQhM/MCGx+skrujF0hfHDIcrFIiP2nKOC81v0yWV9 wFFi9MHoT9tDDHsdCgPfj9FldoYB46rT3rssFgzM71TVkEvU4AacNA9BD+mPbqVU+mAf Wj6hu1oHfI5WgGdStofjUiDf2HS7DmcmpM6Ff20EoWQiZYa7wBMf9z6ghQUG8Essaz7o NK/A== X-Gm-Message-State: ALoCoQny7MpLfauVp5RHDkeDKhwvaR5fYe244lzQpQRVnIyMfHAKE6TGSgWwy+WobGtxf21aWQvE X-Received: by 10.236.180.232 with SMTP id j68mr2204572yhm.122.1395935009350; Thu, 27 Mar 2014 08:43:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.170.162.214 with HTTP; Thu, 27 Mar 2014 08:43:09 -0700 (PDT) In-Reply-To: References: From: Jeff Garzik Date: Thu, 27 Mar 2014 11:43:09 -0400 Message-ID: To: Tamas Blummer Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.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 SPF_PASS SPF: sender matches SPF record -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: 1WTCSs-0006TN-Sv 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:43:36 -0000 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/