summaryrefslogtreecommitdiff
path: root/81/6d0924174d0d040ae77184d5cc9747b9d1b0c3
blob: 9214f58f616609ac944209052a9429e59d6ba0fe (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
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 <jgarzik@exmulti.com>) 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 <bitcoin-development@lists.sourceforge.net>;
	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: <CAKaEYhJ_r7ozQ3v+ggZt35b4GA3+VBkdCy2LVYKoLMGa5bFBfQ@mail.gmail.com>
References: <519AB8EB.5000103@monetize.io>
	<CAKaEYh+eYEApCnbLPZ12RW1XO41epTR4R_nqxM9c3GFHPDEQig@mail.gmail.com>
	<CA+8xBpf04mMER7r-qh40EVbd_Q2pHnf=UMAAOWOhb0dnt_OHww@mail.gmail.com>
	<CAKaEYhJ_r7ozQ3v+ggZt35b4GA3+VBkdCy2LVYKoLMGa5bFBfQ@mail.gmail.com>
Date: Wed, 22 May 2013 10:20:22 -0400
Message-ID: <CA+8xBpc4deHT7uY+N+yx_qOEvLV3T2G7aXqHtq=nRPGd6=2O=g@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: 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 <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:20:29 -0000

On Wed, May 22, 2013 at 10:12 AM, Melvin Carvalho
<melvincarvalho@gmail.com> wrote:
> On 22 May 2013 16:07, Jeff Garzik <jgarzik@exmulti.com> wrote:
>>
>> 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.
>
>
> 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