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 4A1C212B3 for ; Tue, 1 Sep 2015 21:16:40 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from resqmta-po-10v.sys.comcast.net (resqmta-po-10v.sys.comcast.net [96.114.154.169]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 8EDA61A9 for ; Tue, 1 Sep 2015 21:16:39 +0000 (UTC) Received: from resomta-po-06v.sys.comcast.net ([96.114.154.230]) by resqmta-po-10v.sys.comcast.net with comcast id BxGY1r0044yXVJQ01xGeQX; Tue, 01 Sep 2015 21:16:38 +0000 Received: from crushinator.localnet ([IPv6:2601:186:c000:825e:e9f4:8901:87c7:24a0]) by resomta-po-06v.sys.comcast.net with comcast id BxGd1r00J4eLRLv01xGemA; Tue, 01 Sep 2015 21:16:38 +0000 From: Matt Whitlock To: Marco Pontello Date: Tue, 01 Sep 2015 17:16:37 -0400 Message-ID: <5546682.RnG4VcateO@crushinator> User-Agent: KMail/4.14.10 (Linux/4.0.5-gentoo; KDE/4.14.11; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1441142198; bh=+ltiXrAEvCC8Uu9dReFlTs16XP0NALPqij4LvCIYHCY=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=bVMtYbo6wMpW3CJBNVV8myux4Be0g8H1RtCxyex00Mc7I7PXvhDu+uwt8UANDwqBt gatxL/JAW7IXFpL7CNc56qIJjuuMC+5xewA0T8Iv5zlUGBq+dl4d5jzT/v5V+QqLk3 U5Hs8ItCBntKf0c1kHoQEDzu+37ymZFcFoI1KcbjFUVNGDJaRx/PJln16knBnk1B1n SE8O7K3JwdxPKiTlwefEp5Bt4kbkw/n+5Ut8tv2SquBlBDz29TbEgLgNnMattPd2mg NEVHLh7G1sXmCS2nK2d1U7QbioZWgIzCX8p+UJD1ePtcIVg14d+8ToFWqlMa2dCuzI 2jsn6c5bz8CCw== X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE 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 21:16:40 -0000 Isn't this all backward? The "authority" component of the URL should id= entify the chain, and the "path" component should identify the particul= ar block, tx, or address in that chain. So instead of: blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd39= 18f76c17f?chain=3D000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f= 1b60a8ce26f It should be: blockchain://000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a= 8ce26f/tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f76c= 17f And I would agree with allowing well-known chains to register a name, t= o be used as an alternative to the literal, hash syntax: blockchain://bitcoin/tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2= f24ecd3918f76c17f On Tuesday, 1 September 2015, at 4:49 pm, Marco Pontello wrote: > On Sat, Aug 29, 2015 at 10:10 PM, Jorge Tim=F3n < > bitcoin-dev@lists.linuxfoundation.org> wrote: >=20 > > > > 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/3191d5e8e75687a27cf466b7a4= c70bdc04809d39 > > I'm completely fine with doing that using an optional parameter (fo= r > > backwards compatibility). > > >=20 > I see that using the genesis block hash would be the perfectly rigoro= us 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 woul= d > spare a source lookup just to write a correct reference to a tx, mayb= e in a > forum or a post. >=20 > So a reference to a certain tx could be either: >=20 > blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd= 3918f76c17f >=20 > blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd= 3918f76c17f?chain=3D000000000019d6689c085ae165831e934ff763ae46a2a6c172b= 3f1b60a8ce26f >=20 > blockchain://ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd391= 8f76c17f?chain=3Dmain >=20 > (or a different element name maybe) >=20 > --=20 > Try the Online TrID File Identifier > http://mark0.net/onlinetrid.aspx