Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UedH5-0006LW-2b for bitcoin-development@lists.sourceforge.net; Tue, 21 May 2013 03:30:07 +0000 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; Received: from mail-oa0-f47.google.com ([209.85.219.47]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UedH4-0008L1-0W for bitcoin-development@lists.sourceforge.net; Tue, 21 May 2013 03:30:07 +0000 Received: by mail-oa0-f47.google.com with SMTP id m1so196154oag.6 for ; Mon, 20 May 2013 20:30:00 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.182.226.162 with SMTP id rt2mr296304obc.9.1369107000658; Mon, 20 May 2013 20:30:00 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.11.230 with HTTP; Mon, 20 May 2013 20:30:00 -0700 (PDT) Received: by 10.76.11.230 with HTTP; Mon, 20 May 2013 20:30:00 -0700 (PDT) In-Reply-To: References: <519AB8EB.5000103@monetize.io> Date: Mon, 20 May 2013 20:30:00 -0700 X-Google-Sender-Auth: Z_PiV1h240MUXcGII_abhf9fbpc Message-ID: From: Mike Hearn To: Jeff Garzik Content-Type: multipart/alternative; boundary=001a11c2e93c6f1a7d04dd3210f3 X-Spam-Score: -0.5 (/) 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 (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 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: 1UedH4-0008L1-0W Cc: Bitcoin Dev 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 May 2013 03:30:07 -0000 --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" wrote: > On Mon, May 20, 2013 at 7:59 PM, Mark Friedenbach > 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

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 glo= bal naming system that seems like a good compromise between uniqueness and = readability.

On 20 May 2013 19:45, "Jeff Garzik" &l= t;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 w= e
> use Version 4 (random) UUIDs, with the random bits extracted from the<= br> > double-SHA256 hash of the genesis block of the chain. (For colored
> coins, the colored coin definition transaction would be used instead,<= br> > 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. =C2=A0A bitcoin-specific version 6, if you
will.


> And some example chain identifiers:
>
> =C2=A0 =C2=A0 =C2=A0mainnet: =C2=A0UUID('6fe28c0a-b6f1-4372-81a6-a= 246ae63f74f')
> =C2=A0 =C2=A0 =C2=A0testnet3: UUID('43497fd7-f826-4571-88f4-a30fd9= cec3ae')
> =C2=A0 =C2=A0 =C2=A0namecoin: UUID('70c7a9f0-a2fb-4d48-a635-a70d5b= 157c80')

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-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment
--001a11c2e93c6f1a7d04dd3210f3--