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
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
|
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 <melvincarvalho@gmail.com>) id 1Uf9mc-0006lk-47
for bitcoin-development@lists.sourceforge.net;
Wed, 22 May 2013 14:12:50 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.215.53 as permitted sender)
client-ip=209.85.215.53; envelope-from=melvincarvalho@gmail.com;
helo=mail-la0-f53.google.com;
Received: from mail-la0-f53.google.com ([209.85.215.53])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Uf9mb-0005Bp-AN
for bitcoin-development@lists.sourceforge.net;
Wed, 22 May 2013 14:12:50 +0000
Received: by mail-la0-f53.google.com with SMTP id ea20so1990643lab.26
for <bitcoin-development@lists.sourceforge.net>;
Wed, 22 May 2013 07:12:42 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.112.132.163 with SMTP id ov3mr4194699lbb.48.1369231962579;
Wed, 22 May 2013 07:12:42 -0700 (PDT)
Received: by 10.112.143.38 with HTTP; Wed, 22 May 2013 07:12:42 -0700 (PDT)
In-Reply-To: <CA+8xBpf04mMER7r-qh40EVbd_Q2pHnf=UMAAOWOhb0dnt_OHww@mail.gmail.com>
References: <519AB8EB.5000103@monetize.io>
<CAKaEYh+eYEApCnbLPZ12RW1XO41epTR4R_nqxM9c3GFHPDEQig@mail.gmail.com>
<CA+8xBpf04mMER7r-qh40EVbd_Q2pHnf=UMAAOWOhb0dnt_OHww@mail.gmail.com>
Date: Wed, 22 May 2013 16:12:42 +0200
Message-ID: <CAKaEYhJ_r7ozQ3v+ggZt35b4GA3+VBkdCy2LVYKoLMGa5bFBfQ@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
To: Jeff Garzik <jgarzik@exmulti.com>
Content-Type: multipart/alternative; boundary=047d7b3a8236beaa5904dd4f2837
X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(melvincarvalho[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1Uf9mb-0005Bp-AN
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:12:50 -0000
--047d7b3a8236beaa5904dd4f2837
Content-Type: text/plain; charset=ISO-8859-1
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
>
> --
> Jeff Garzik
> exMULTI, Inc.
> jgarzik@exmulti.com
>
--047d7b3a8236beaa5904dd4f2837
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On 22 May 2013 16:07, Jeff Garzik <span dir=3D"ltr"><<a href=3D"=
mailto:jgarzik@exmulti.com" target=3D"_blank">jgarzik@exmulti.com</a>></=
span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Wed, May 22, 2013 at 6:=
27 AM, Melvin Carvalho<br>
<<a href=3D"mailto:melvincarvalho@gmail.com">melvincarvalho@gmail.com</a=
>> wrote:<br>
> Some out of band algo/hash could work so long as there was a one to on=
e<br>
> relationship between the described object and the UUID. =A0In this cas=
e the<br>
> gensis block may not uniquely identify a coin.<br>
<br>
</div>What does this mean? =A0It seems extremely unlikely that two differen=
t<br>
genesis blocks will have the same hash.<br></blockquote><div><br></div><div=
>Two coin ecosystems could have the same genesis block<br></div><div>=A0</d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">
<div class=3D"HOEnZb"><div class=3D"h5"><br>
--<br>
Jeff Garzik<br>
exMULTI, Inc.<br>
<a href=3D"mailto:jgarzik@exmulti.com">jgarzik@exmulti.com</a><br>
</div></div></blockquote></div><br></div></div>
--047d7b3a8236beaa5904dd4f2837--
|
