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 0A54910B4 for ; Tue, 1 Sep 2015 21:44:02 +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 06CD61B0 for ; Tue, 1 Sep 2015 21:43:59 +0000 (UTC) Received: by lbpo4 with SMTP id o4so7547184lbp.2 for ; Tue, 01 Sep 2015 14:43:58 -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=oGtmUb8ZMmCWkDLpZnOpcum3R/0FuObRPSnt/Kbv4Jw=; b=AlcrIvN+cyRGrYzSfcsbAP9nRzCO3dnVcR7/NvPXyFrgUslQNqxMyI9OHRvqaHOMMh A8D/btZogHlakcrLXlp2IxJ5vQloQ3tXKMGeu7426TM6GeYei9EqwcecdRoKJ3yrFHjl PER0i2LW/33CqkTEl4MOrRFBOA5COMstu+MNzzBJ7KrF05/ItzSOF7Ke3ePi588fRoOy aZe4JOmi6qjUG8neg2NNKrWucetjreDRmbEmzTlJ/hHtuldQRMAA27RZsRE9QG6aLKfl SmltjFmHiIi6sNpjUpRuMVVmKrNGkXM9/0E+19EksjYDzXBNIsVTQ5dpOua7tlGANKXq aWXw== X-Received: by 10.112.129.72 with SMTP id nu8mr9731017lbb.81.1441143838571; Tue, 01 Sep 2015 14:43:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.114.186.168 with HTTP; Tue, 1 Sep 2015 14:43:39 -0700 (PDT) In-Reply-To: <1842396.ZYjkpCDfSt@crushinator> References: <5546682.RnG4VcateO@crushinator> <1842396.ZYjkpCDfSt@crushinator> From: Marco Pontello Date: Tue, 1 Sep 2015 23:43:39 +0200 Message-ID: To: Matt Whitlock Content-Type: multipart/alternative; boundary=047d7b3a8c60918618051eb67230 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 21:44:02 -0000 --047d7b3a8c60918618051eb67230 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Oh, my bad! Right, sounds pretty good to me then. On Tue, Sep 1, 2015 at 11:42 PM, Matt Whitlock wrote: > The authority part in a URI is optional. > > > blockchain:/tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f= 76c17f > > Notice the lack of a double-slash. > > > On Tuesday, 1 September 2015, at 11:38 pm, Marco Pontello wrote: > > I see your point. But I personally like that the chain part could be > > optional, given that the vast majority of the references in the end wil= l > be > > to Bitcoin main net. > > > > On Tue, Sep 1, 2015 at 11:16 PM, Matt Whitlock > > wrote: > > > > > Isn't this all backward? The "authority" component of the URL should > > > identify the chain, and the "path" component should identify the > particular > > > block, tx, or address in that chain. > > > > > > So instead of: > > > > > > > > > > blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918= f76c17f?chain=3D000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8= ce26f > > > > > > It should be: > > > > > > > > > > blockchain://000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8c= e26f/tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f76c17f > > > > > > And I would agree with allowing well-known chains to register a name, > to > > > be used as an alternative to the literal, hash syntax: > > > > > > > > > > blockchain://bitcoin/tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f2= 4ecd3918f76c17f > > > > > > > > > On Tuesday, 1 September 2015, at 4:49 pm, Marco Pontello wrote: > > > > 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/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918= f76c17f > > > > > > > > > > > > blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918= f76c17f?chain=3D000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8= ce26f > > > > > > > > > > > > blockchain://ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f76= c17f?chain=3Dmain > > > > > > > > (or a different element name maybe) > > > > > > > > -- > > > > Try the Online TrID File Identifier > > > > http://mark0.net/onlinetrid.aspx > > > > > > > > > > > -- > > Try the Online TrID File Identifier > > http://mark0.net/onlinetrid.aspx > --=20 Try the Online TrID File Identifier http://mark0.net/onlinetrid.aspx --047d7b3a8c60918618051eb67230 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Oh, my bad! Right, sounds pretty good to me then.

On Tue, Sep 1, 2015 = at 11:42 PM, Matt Whitlock <bip@mattwhitlock.name> wrote= :
The authority part in a URI is optional= .

blockchain:/tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f76= c17f

Notice the lack of a double-slash.


On Tuesday, 1 September 2015, at 11:38 pm, Marco Pontello wrote:
> I see your point. But I personally like that the chain part could be > optional, given that the vast majority of the references in the end wi= ll be
> to Bitcoin main net.
>
> On Tue, Sep 1, 2015 at 11:16 PM, Matt Whitlock <bip@mattwhitlock.name>
> wrote:
>
> > Isn't this all backward? The "authority" component = of the URL should
> > identify the chain, and the "path" component should ide= ntify the particular
> > block, tx, or address in that chain.
> >
> > So instead of:
> >
> >
> > blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f2= 4ecd3918f76c17f?chain=3D000000000019d6689c085ae165831e934ff763ae46a2a6c172b= 3f1b60a8ce26f
> >
> > It should be:
> >
> >
> > blockchain://000000000019d6689c085ae165831e934ff763ae46a2a6c172b3= f1b60a8ce26f/tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f7= 6c17f
> >
> > And I would agree with allowing well-known chains to register a n= ame, to
> > be used as an alternative to the literal, hash syntax:
> >
> >
> > blockchain://bitcoin/tx/ca26cedeb9cbc94e030891578e0d2b688a2890211= 4f6ad2f24ecd3918f76c17f
> >
> >
> > On Tuesday, 1 September 2015, at 4:49 pm, Marco Pontello wrote: > > > On Sat, Aug 29, 2015 at 10:10 PM, Jorge Tim=C3=B3n <
> > > bit= coin-dev@lists.linuxfoundation.org> wrote:
> > >
> > > >
> > > > I would really prefer chain=3D<chainID> over netw= ork=3D<chainPetnameStr>
> > > > By chainID I mean the hash of the genesis block, see > > > >
> > > >
> > https://g= ithub.com/jtimon/bitcoin/commit/3191d5e8e75687a27cf466b7a4c70bdc04809d39
> > > > I'm completely fine with doing that using an option= al parameter (for
> > > > backwards compatibility).
> > > >
> > >
> > > I see that using the genesis block hash would be the perfect= ly rigorous
> > way
> > > to do it, but what do you think about the possibility of let= ting 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/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f2= 4ecd3918f76c17f
> > >
> > >
> > blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f2= 4ecd3918f76c17f?chain=3D000000000019d6689c085ae165831e934ff763ae46a2a6c172b= 3f1b60a8ce26f
> > >
> > >
> > blockchain://ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ec= d3918f76c17f?chain=3Dmain
> > >
> > > (or a different element name maybe)
> > >
> > > --
> > > Try the Online TrID File Identifier
> > > http://mark0.net/onlinetrid.aspx
> >
>
>
>
> --
> Try the Online TrID File Identifier
> http://mark0.net/onlinetrid.aspx



--
=
Try the Online TrID File Identifier
http://mark0.net/= onlinetrid.aspx
--047d7b3a8c60918618051eb67230--