Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.219.47 as permitted sender)
	client-ip=209.85.219.47; envelope-from=mh.in.england@gmail.com;
	helo=mail-oa0-f47.google.com; 
MIME-Version: 1.0
Sender: mh.in.england@gmail.com
In-Reply-To: <CA+8xBpeUOsZq=3jP7GMJgnxH1Vh9GmPydzXWuScCjDyVUf2YVg@mail.gmail.com>
References: <519AB8EB.5000103@monetize.io>
	<CA+8xBpeUOsZq=3jP7GMJgnxH1Vh9GmPydzXWuScCjDyVUf2YVg@mail.gmail.com>
Date: Mon, 20 May 2013 20:30:00 -0700
Message-ID: <CANEZrP10UpCEKFZiTrnRJxiwJW6tmfZRLJpYzVceew5tXXugaw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Jeff Garzik <jgarzik@exmulti.com>
Content-Type: multipart/alternative; boundary=001a11c2e93c6f1a7d04dd3210f3
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] UUID to identify chains (payment protocol
 and elsewhere)
Precedence: list

--001a11c2e93c6f1a7d04dd3210f3
Content-Type: text/plain; charset=UTF-8

Bitcoinj already has such chain id's and we use standard Java style reverse
DNS names: org.bitcoin.main, etc. If we want a more global naming system
that seems like a good compromise between uniqueness and readability.
On 20 May 2013 19:45, "Jeff Garzik" <jgarzik@exmulti.com> wrote:

> On Mon, May 20, 2013 at 7:59 PM, Mark Friedenbach <mark@monetize.io>
> wrote:
> > So as to remain reasonably compliant with RFC 4122, I recommend that we
> > use Version 4 (random) UUIDs, with the random bits extracted from the
> > double-SHA256 hash of the genesis block of the chain. (For colored
> > coins, the colored coin definition transaction would be used instead,
> > but I will address that in a separate proposal and will say just one
> > thing about it: adopting this method for identifying chains/coins will
> > greatly assist in adopting the payment protocol to colored coins.)
>
> This proposal seems closer to Version 5 than Version 4, in spirit.
> But given that useful content may be deduced from UUID, it is not
> truly applicable to either.  A bitcoin-specific version 6, if you
> will.
>
>
> > And some example chain identifiers:
> >
> >      mainnet:  UUID('6fe28c0a-b6f1-4372-81a6-a246ae63f74f')
> >      testnet3: UUID('43497fd7-f826-4571-88f4-a30fd9cec3ae')
> >      namecoin: UUID('70c7a9f0-a2fb-4d48-a635-a70d5b157c80')
>
> Note that, as this example unintentionally implies, humans are going
> to want a side-by-side mapping /anyway/, just to make it readable and
> usable to humans.
>
> Almost all useful multi-chain software will require a readable
> shortname string anyway, the thing this proposal wishes to avoid.
>
> --
> Jeff Garzik
> exMULTI, Inc.
> jgarzik@exmulti.com
>
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

--001a11c2e93c6f1a7d04dd3210f3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">Bitcoinj already has such chain id&#39;s and we use standard=
 Java style reverse DNS names: org.bitcoin.main, etc. If we want a more glo=
bal naming system that seems like a good compromise between uniqueness and =
readability.</p>

<div class=3D"gmail_quote">On 20 May 2013 19:45, &quot;Jeff Garzik&quot; &l=
t;<a href=3D"mailto:jgarzik@exmulti.com">jgarzik@exmulti.com</a>&gt; wrote:=
<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Mon, May 20, 2013 at 7:59 PM, Mark Friedenbach &lt;<a href=3D"mailto:mar=
k@monetize.io">mark@monetize.io</a>&gt; wrote:<br>
&gt; So as to remain reasonably compliant with RFC 4122, I recommend that w=
e<br>
&gt; use Version 4 (random) UUIDs, with the random bits extracted from the<=
br>
&gt; double-SHA256 hash of the genesis block of the chain. (For colored<br>
&gt; coins, the colored coin definition transaction would be used instead,<=
br>
&gt; but I will address that in a separate proposal and will say just one<b=
r>
&gt; thing about it: adopting this method for identifying chains/coins will=
<br>
&gt; greatly assist in adopting the payment protocol to colored coins.)<br>
<br>
This proposal seems closer to Version 5 than Version 4, in spirit.<br>
But given that useful content may be deduced from UUID, it is not<br>
truly applicable to either. =C2=A0A bitcoin-specific version 6, if you<br>
will.<br>
<br>
<br>
&gt; And some example chain identifiers:<br>
&gt;<br>
&gt; =C2=A0 =C2=A0 =C2=A0mainnet: =C2=A0UUID(&#39;6fe28c0a-b6f1-4372-81a6-a=
246ae63f74f&#39;)<br>
&gt; =C2=A0 =C2=A0 =C2=A0testnet3: UUID(&#39;43497fd7-f826-4571-88f4-a30fd9=
cec3ae&#39;)<br>
&gt; =C2=A0 =C2=A0 =C2=A0namecoin: UUID(&#39;70c7a9f0-a2fb-4d48-a635-a70d5b=
157c80&#39;)<br>
<br>
Note that, as this example unintentionally implies, humans are going<br>
to want a side-by-side mapping /anyway/, just to make it readable and<br>
usable to humans.<br>
<br>
Almost all useful multi-chain software will require a readable<br>
shortname string anyway, the thing this proposal wishes to avoid.<br>
<br>
--<br>
Jeff Garzik<br>
exMULTI, Inc.<br>
<a href=3D"mailto:jgarzik@exmulti.com">jgarzik@exmulti.com</a><br>
<br>
---------------------------------------------------------------------------=
---<br>
Try New Relic Now &amp; We&#39;ll Send You this Cool Shirt<br>
New Relic is the only SaaS-based application performance monitoring service=
<br>
that delivers powerful full stack analytics. Optimize and monitor your<br>
browser, app, &amp; servers with just a few lines of code. Try New Relic<br=
>
and get this awesome Nerd Life shirt! <a href=3D"http://p.sf.net/sfu/newrel=
ic_d2d_may" target=3D"_blank">http://p.sf.net/sfu/newrelic_d2d_may</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div>

--001a11c2e93c6f1a7d04dd3210f3--