From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UecZk-0004gU-Sq for bitcoin-development@lists.sourceforge.net; Tue, 21 May 2013 02:45:20 +0000 X-ACL-Warn: Received: from mail-pa0-f48.google.com ([209.85.220.48]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UecZj-0003hM-Sp for bitcoin-development@lists.sourceforge.net; Tue, 21 May 2013 02:45:20 +0000 Received: by mail-pa0-f48.google.com with SMTP id kp6so217041pab.35 for ; Mon, 20 May 2013 19:45:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=2o+dzL79o5t2eBkE7ySzfL9Js4/2y2+gpIPl04WcIvs=; b=TXTrMMqLMbeJiCH57jSFYzh7dTDZYxa9r4O8m77DpjyPZv8TfFwGTruqdv7fbnAjcB 28kFE7ZOph/SzO5ck4Gn0iUWHwSPkvuWYLdzVfSRH6X6gP9N5Gj6x4axYYlNULHGTYFa QSqXDx7nbH5mpHXlCtsplSlcJvp/ORIHoHy2boOegq1RovKe7B+43WcAkL2azBNwCsT8 nXTZK4CJos2mAAYFgDXHss59jcEHI5iWa2tPWmVPujMUvoWVQWDO0fRzEHMzjfx1HPxe F21QJLgHXm6dUeACkeKUizlM30VW+s6TYcF/4SbRWJIVCKG0iFq4+4KxP/9XSIZgJBaz +loA== MIME-Version: 1.0 X-Received: by 10.66.159.66 with SMTP id xa2mr987104pab.36.1369104313982; Mon, 20 May 2013 19:45:13 -0700 (PDT) Received: by 10.68.15.194 with HTTP; Mon, 20 May 2013 19:45:13 -0700 (PDT) X-Originating-IP: [24.30.48.124] In-Reply-To: <519AB8EB.5000103@monetize.io> References: <519AB8EB.5000103@monetize.io> Date: Mon, 20 May 2013 22:45:13 -0400 Message-ID: From: Jeff Garzik To: Mark Friedenbach Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQlcTN8SdbHY+tQ7o9tcKkJodsYGqNvsWB43Vgiea0+0leFAsd8eWsSc4Z7JnXctUZMSdSkb X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1UecZj-0003hM-Sp Cc: bitcoin-development@lists.sourceforge.net 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 02:45:21 -0000 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