From: Melvin Carvalho <melvincarvalho@gmail•com>
To: Jeff Garzik <jgarzik@exmulti•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] UUID to identify chains (payment protocol and elsewhere)
Date: Wed, 22 May 2013 16:12:42 +0200 [thread overview]
Message-ID: <CAKaEYhJ_r7ozQ3v+ggZt35b4GA3+VBkdCy2LVYKoLMGa5bFBfQ@mail.gmail.com> (raw)
In-Reply-To: <CA+8xBpf04mMER7r-qh40EVbd_Q2pHnf=UMAAOWOhb0dnt_OHww@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 591 bytes --]
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
>
[-- Attachment #2: Type: text/html, Size: 1261 bytes --]
next prev parent reply other threads:[~2013-05-22 14:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 23:59 Mark Friedenbach
2013-05-21 2:45 ` Jeff Garzik
2013-05-21 3:30 ` Mike Hearn
2013-05-21 4:00 ` Mark Friedenbach
2013-05-21 4:04 ` Luke-Jr
2013-05-22 10:27 ` Melvin Carvalho
2013-05-22 14:07 ` Jeff Garzik
2013-05-22 14:12 ` Melvin Carvalho [this message]
2013-05-22 14:20 ` Jeff Garzik
2013-05-22 14:29 ` Luke-Jr
2013-05-22 14:55 ` Jeff Garzik
2013-05-22 15:59 ` Gavin Andresen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKaEYhJ_r7ozQ3v+ggZt35b4GA3+VBkdCy2LVYKoLMGa5bFBfQ@mail.gmail.com \
--to=melvincarvalho@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@exmulti$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox