From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Uf9u1-00078L-Bn for bitcoin-development@lists.sourceforge.net; Wed, 22 May 2013 14:20:29 +0000 X-ACL-Warn: Received: from mail-pb0-f50.google.com ([209.85.160.50]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Uf9u0-0005mz-KW for bitcoin-development@lists.sourceforge.net; Wed, 22 May 2013 14:20:29 +0000 Received: by mail-pb0-f50.google.com with SMTP id wy17so1746366pbc.37 for ; Wed, 22 May 2013 07:20:22 -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=x3xzZTxYWsejWZYOvk1CQMoJltPJBda4cvh9/VuTDno=; b=j0JxHswEES7Ktplj5Pll6K0k+pL+opzWhvfR5VeQiT/JTaw11M8Yc8jxLZ/JEtc4vY QQINqtmvKgD9sEZxiYfwV2epX9W2bETGCLalldBTraL93ggUkC5fg+qXX0uoLL2j69mf HDH22G1ZE+ZxzpgpLXyA768HNzeAkCXNsakBhKBE0xpwqbRQ7ZLLv81ks9KLFR8pjMSV e5bvns8Y4OM/LKvF5pOLkKkAFftY6KxKKK6uonD2z7pD/V+FFMx+tMKZj07QgIcz0KOg aRU18N1NJWbx9sPyfAp9Nl1cOSR9ejh93qRNOzfGc1K+YqkPKqNWX3Qtj2Wf3JBl7upR dV1g== MIME-Version: 1.0 X-Received: by 10.66.164.232 with SMTP id yt8mr8595851pab.21.1369232422756; Wed, 22 May 2013 07:20:22 -0700 (PDT) Received: by 10.68.15.194 with HTTP; Wed, 22 May 2013 07:20:22 -0700 (PDT) X-Originating-IP: [66.194.102.6] In-Reply-To: References: <519AB8EB.5000103@monetize.io> Date: Wed, 22 May 2013 10:20:22 -0400 Message-ID: From: Jeff Garzik To: Melvin Carvalho Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkUsCakIDTX+pdafrUAH1lbL8OGPeyRo/KnJ9n1i1DURxnSs+1SnFA99fo6SgBXd2x1Prn0 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: 1Uf9u0-0005mz-KW Cc: Bitcoin Dev 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 May 2013 14:20:29 -0000 On Wed, May 22, 2013 at 10:12 AM, Melvin Carvalho wrote: > On 22 May 2013 16:07, Jeff Garzik wrote: >> >> On Wed, May 22, 2013 at 6:27 AM, Melvin Carvalho >> 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. > > > Two coin ecosystems could have the same genesis block That has really, really bad side effects. The whole point of the bitcoin consensus algorithm is to avoid situations like this. We don't want to encourage that behavior with code. -- Jeff Garzik exMULTI, Inc. jgarzik@exmulti.com