📅 Original date posted:2013-05-22
📝 Original message:On Wed, May 22, 2013 at 10:12 AM, Melvin Carvalho
<melvincarvalho at gmail.com> wrote:
> On 22 May 2013 16:07, Jeff Garzik <jgarzik at exmulti.com> wrote:
>>
>> On Wed, May 22, 2013 at 6:27 AM, Melvin Carvalho
>> <melvincarvalho at 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 at exmulti.com
Jeff Garzik [ARCHIVE] /
npub1kf…f3f58
2023-06-07 15:02:12
in reply to nevent1q…sspn
Author Public Key
npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58Published at
2023-06-07 15:02:12Event JSON
{
"id": "6c45f24cb026fc76044acc2f38e3461d911fc74ffc9d109d6d79865710ebd678",
"pubkey": "b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11",
"created_at": 1686150132,
"kind": 1,
"tags": [
[
"e",
"f48f714526d322379c9590ee7300f610f029d3880329fd3820bde032fc049d84",
"",
"root"
],
[
"e",
"1a5e649dd030d70880323e954f3843aa0e5d0055625f83a56a7148b6ba06ce04",
"",
"reply"
],
[
"p",
"e316966328c4cb66c34719ef9a7b3bc54ef601663ad4ab06185991237735aa19"
]
],
"content": "📅 Original date posted:2013-05-22\n📝 Original message:On Wed, May 22, 2013 at 10:12 AM, Melvin Carvalho\n\u003cmelvincarvalho at gmail.com\u003e wrote:\n\u003e On 22 May 2013 16:07, Jeff Garzik \u003cjgarzik at exmulti.com\u003e wrote:\n\u003e\u003e\n\u003e\u003e On Wed, May 22, 2013 at 6:27 AM, Melvin Carvalho\n\u003e\u003e \u003cmelvincarvalho at gmail.com\u003e wrote:\n\u003e\u003e \u003e Some out of band algo/hash could work so long as there was a one to one\n\u003e\u003e \u003e relationship between the described object and the UUID. In this case\n\u003e\u003e \u003e the\n\u003e\u003e \u003e gensis block may not uniquely identify a coin.\n\u003e\u003e\n\u003e\u003e What does this mean? It seems extremely unlikely that two different\n\u003e\u003e genesis blocks will have the same hash.\n\u003e\n\u003e\n\u003e Two coin ecosystems could have the same genesis block\n\nThat has really, really bad side effects. The whole point of the\nbitcoin consensus algorithm is to avoid situations like this.\n\nWe don't want to encourage that behavior with code.\n\n-- \nJeff Garzik\nexMULTI, Inc.\njgarzik at exmulti.com",
"sig": "adcc041c984475d757b22c860387d5c0bb111836d07931e5a882f3df18a18b9791d4139a8f356cf78a916d468c5f7ad59d47c384684be6d8086462be322a8a6a"
}