Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <jgarzik@exmulti.com>) id 1Uf9hu-0005C4-2V
	for bitcoin-development@lists.sourceforge.net;
	Wed, 22 May 2013 14:07:58 +0000
X-ACL-Warn: 
Received: from mail-pb0-f50.google.com ([209.85.160.50])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Uf9ht-0004Fz-1q
	for bitcoin-development@lists.sourceforge.net;
	Wed, 22 May 2013 14:07:57 +0000
Received: by mail-pb0-f50.google.com with SMTP id wy17so1724055pbc.9
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 22 May 2013 07:07:51 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:in-reply-to:references:date
	:message-id:subject:from:to:cc:content-type:x-gm-message-state;
	bh=JFMk+qyCcAc8s7ndlilpzGZX707MN5r71ICA5bno7j0=;
	b=fLmyPwC8P/1rC7gSMrjah0THwuCqZSMKPBqIn3rNfN+GKJ+XHxOBNQAAA4T1LprZ+k
	xEb+RdMRFW+vhCHBc7frlGwyWKVo9Wj2gDVwXo0dUA32NhI+f0R5+zeipIGDbptXBXf1
	Mjw4JepmU8A6v7+u6OYY6dKuioGEdOoRdJoumzA/vz4+Soi8MrDoHl4zyHT98aPZIrjE
	xI53Lcyh7034VDjzRWsEFA5Dm7Kn7eKbb5uYllI3evap/couF2/jxh24mpCgQs579wmW
	8bImEwb4XBnC9aqLGWx1cnxaN53wNuluIyQyGUd8E2MFcFatuM1C7ZQnOgVdgHrfFWUP
	G2uQ==
MIME-Version: 1.0
X-Received: by 10.68.191.36 with SMTP id gv4mr8144797pbc.67.1369231671175;
	Wed, 22 May 2013 07:07:51 -0700 (PDT)
Received: by 10.68.15.194 with HTTP; Wed, 22 May 2013 07:07:51 -0700 (PDT)
X-Originating-IP: [66.194.102.6]
In-Reply-To: <CAKaEYh+eYEApCnbLPZ12RW1XO41epTR4R_nqxM9c3GFHPDEQig@mail.gmail.com>
References: <519AB8EB.5000103@monetize.io>
	<CAKaEYh+eYEApCnbLPZ12RW1XO41epTR4R_nqxM9c3GFHPDEQig@mail.gmail.com>
Date: Wed, 22 May 2013 10:07:51 -0400
Message-ID: <CA+8xBpf04mMER7r-qh40EVbd_Q2pHnf=UMAAOWOhb0dnt_OHww@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: Melvin Carvalho <melvincarvalho@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQlllNNT2LSftdyT8vyr3cNCkhzDtbBicgmXeTEdsQsUqWuOsaT97JzVJKhnffYow5PBz6Vq
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1Uf9ht-0004Fz-1q
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] UUID to identify chains (payment protocol
 and elsewhere)
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: Wed, 22 May 2013 14:07:58 -0000

On Wed, May 22, 2013 at 6:27 AM, Melvin Carvalho
<melvincarvalho@gmail.com> wrote:
> Some out of band algo/hash could work so long as there was a one to one
> relationship between the described object and the UUID.  In this case the
> gensis block may not uniquely identify a coin.

What does this mean?  It seems extremely unlikely that two different
genesis blocks will have the same hash.

-- 
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com