From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 8436413F7 for ; Tue, 1 Sep 2015 14:50:10 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-lb0-f174.google.com (mail-lb0-f174.google.com [209.85.217.174]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id B38D0234 for ; Tue, 1 Sep 2015 14:50:09 +0000 (UTC) Received: by lbpo4 with SMTP id o4so1090658lbp.2 for ; Tue, 01 Sep 2015 07:50:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=F9/aBg+Szfw6pm24+L6U6ta8il7BfGIOGIB7NMLIA64=; b=yvgsaQmPO1UUcKWNpWbuiz/kJ2nnlcKySKILL1JWTOp3dq7y3UPVeZQpF0ZZkyfmKm Up/tmYyf8DoK4TGGqZA0KVGQ1yGtk5HElkigwr4WZTdZuPrZdUJvgsKTO03eXn9bA+gO I3XRZvTsZgausbnSEDkTMsERbTJ5R7XwTy/te6qcmzYthC8vARr7xnamvaWu+jrFwEvN pqbqktwqf2t+e+TVML5VdX2/6cGuGqBPEsOtLQBIuypfXljFQXk7KFOH7fZfNIv7VN8g pMR2M52nZulYSESCabeoAETT0YkkCEe1F5sfjuAVG0efuVPNyLNWbRdYsl7dqQQFxcAc Vqeg== X-Received: by 10.112.129.72 with SMTP id nu8mr8851529lbb.81.1441119006975; Tue, 01 Sep 2015 07:50:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.114.186.168 with HTTP; Tue, 1 Sep 2015 07:49:47 -0700 (PDT) In-Reply-To: References: <2509151.XgrrNGsCxR@crushinator> From: Marco Pontello Date: Tue, 1 Sep 2015 16:49:47 +0200 Message-ID: To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= Content-Type: multipart/alternative; boundary=047d7b3a8c607d7053051eb0aace X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: Bitcoin Dev Subject: Re: [bitcoin-dev] RFC - BIP: URI scheme for Blockchain exploration X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Sep 2015 14:50:10 -0000 --047d7b3a8c607d7053051eb0aace Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sat, Aug 29, 2015 at 10:10 PM, Jorge Tim=C3=B3n < bitcoin-dev@lists.linuxfoundation.org> wrote: > > I would really prefer chain=3D over network=3D > By chainID I mean the hash of the genesis block, see > > https://github.com/jtimon/bitcoin/commit/3191d5e8e75687a27cf466b7a4c70bdc= 04809d39 > I'm completely fine with doing that using an optional parameter (for > backwards compatibility). > I see that using the genesis block hash would be the perfectly rigorous way to do it, but what do you think about the possibility of letting also use the name constants, as a simple / more relaxed alternative? That would spare a source lookup just to write a correct reference to a tx, maybe in a forum or a post. So a reference to a certain tx could be either: blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f7= 6c17f blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f7= 6c17f?chain=3D000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce= 26f blockchain://ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f76c1= 7f?chain=3Dmain (or a different element name maybe) --=20 Try the Online TrID File Identifier http://mark0.net/onlinetrid.aspx --047d7b3a8c607d7053051eb0aace Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On Sat, Aug 29, 2015 at 10:10 PM, Jorge Tim=C3=B3n <bi= tcoin-dev@lists.linuxfoundation.org> wrote:

I would really prefer chain=3D<chainID> over network=3D<cha= inPetnameStr>
By chainID I mean the hash of the genesis block, see
https://github.com/= jtimon/bitcoin/commit/3191d5e8e75687a27cf466b7a4c70bdc04809d39
I'm completely fine with doing that using an optional parameter (for backwards compatibility).

I see t= hat using the genesis block hash would be the perfectly rigorous way to do = it, but what do you think about the possibility of letting also use the nam= e constants, as a simple / more relaxed alternative? That would spare a sou= rce lookup just to write a correct reference to a tx, maybe in a forum or a= post.

So a reference to a certain tx could be eit= her:=C2=A0

blockchain://tx/ca26cedeb9cbc94e030891578e0d= 2b688a28902114f6ad2f24ecd3918f76c17f

blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918= f76c17f?chain=3D000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8= ce26f

blockchain://ca26cedeb9cbc94e= 030891578e0d2b688a28902114f6ad2f24ecd3918f76c17f?chain=3Dmain

(or a different element name maybe)

--
Try the Online TrID File Identifier
http://mark0.net/online= trid.aspx
--047d7b3a8c607d7053051eb0aace--