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
|
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 <luke@dashjr.org>) id 1UfA3O-0003TX-1n
for bitcoin-development@lists.sourceforge.net;
Wed, 22 May 2013 14:30:10 +0000
X-ACL-Warn:
Received: from zinan.dashjr.org ([173.242.112.54])
by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1UfA3K-0007nA-Qf for bitcoin-development@lists.sourceforge.net;
Wed, 22 May 2013 14:30:10 +0000
Received: from ishibashi.localnet (unknown
[IPv6:2001:470:5:265:222:4dff:fe50:4c49])
(Authenticated sender: luke-jr)
by zinan.dashjr.org (Postfix) with ESMTPSA id 54E7727A2965;
Wed, 22 May 2013 14:29:53 +0000 (UTC)
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Date: Wed, 22 May 2013 14:29:47 +0000
User-Agent: KMail/1.13.7 (Linux/3.9.0-gentoo; KDE/4.10.2; x86_64; ; )
References: <519AB8EB.5000103@monetize.io>
<CAKaEYhJ_r7ozQ3v+ggZt35b4GA3+VBkdCy2LVYKoLMGa5bFBfQ@mail.gmail.com>
<CA+8xBpc4deHT7uY+N+yx_qOEvLV3T2G7aXqHtq=nRPGd6=2O=g@mail.gmail.com>
In-Reply-To: <CA+8xBpc4deHT7uY+N+yx_qOEvLV3T2G7aXqHtq=nRPGd6=2O=g@mail.gmail.com>
X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F
X-PGP-Key-ID: BD02942421F4889F
X-PGP-Keyserver: hkp://pgp.mit.edu
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201305221429.49704.luke@dashjr.org>
X-Spam-Score: -1.1 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.1 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
X-Headers-End: 1UfA3K-0007nA-Qf
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:30:10 -0000
On Wednesday, May 22, 2013 2:20:22 PM Jeff Garzik wrote:
> 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.
In some cases, multiple currencies can use the same blockchain (not just the
singular genesis block). This use case *is* something we want to encourage -
no reason for people to make an entirely new blockchain if their altcoin fits
within the scope of Bitcoin or another existing altchain.
|
