From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] UUID to identify chains (payment protocol and elsewhere)
Date: Wed, 22 May 2013 14:29:47 +0000 [thread overview]
Message-ID: <201305221429.49704.luke@dashjr.org> (raw)
In-Reply-To: <CA+8xBpc4deHT7uY+N+yx_qOEvLV3T2G7aXqHtq=nRPGd6=2O=g@mail.gmail.com>
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.
next prev parent reply other threads:[~2013-05-22 14:30 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
2013-05-22 14:20 ` Jeff Garzik
2013-05-22 14:29 ` Luke-Jr [this message]
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=201305221429.49704.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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