path: root/2c/05eedb085815d31daf2a8b8a94c2c7183307af

Return-Path: <marcopon@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 2777F1032
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue,  1 Sep 2015 21:39:20 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-la0-f41.google.com (mail-la0-f41.google.com
	[209.85.215.41])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 4AB6315C
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue,  1 Sep 2015 21:39:19 +0000 (UTC)
Received: by lamp12 with SMTP id p12so8919373lam.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 01 Sep 2015 14:39:17 -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=rpo4cLznIcaFJyJtDH2KvA0hCffwsZxfBmcDszC1eso=;
	b=N7OAVz1isgs/xCmzo2mR6IHsawVZk55Y6tC/4fk/qRDw2januLv9Kg/1SSIkT6kN83
	LkdTylyBDXKbb1jWuiw6JM7l0hCt/YqdZsauine+6DgJm311cKZk2jNc37676NN8O0Xe
	IoFI1IHE7V+tue5gXaeanwpRyUmNPy4vZ+7Y76m61EQ9UxSDq+Q/WvsoTD+SQBES2Ux5
	1x1qR+tJk2lZsWSKUunM4mYwtF221oP/hS/WVLNKGy4hfuhElaQRM1JOy7H62iGR5c35
	TYuyYT2UTmjk1T3ggh3T5Fg4/xW+YSdhPeA/bK618OPxB6VBbtM03R89E345c9ZCKrE1
	rCoA==
X-Received: by 10.112.142.105 with SMTP id rv9mr14107526lbb.11.1441143557620; 
	Tue, 01 Sep 2015 14:39:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.114.186.168 with HTTP; Tue, 1 Sep 2015 14:38:58 -0700 (PDT)
In-Reply-To: <5546682.RnG4VcateO@crushinator>
References: <CAE0pACLMcMzHkA=vEx+fiEmq7FA1bXDc4t_hQ+955=r=62V5=g@mail.gmail.com>
	<CABm2gDpC55dsr4GNAUabgnOeXcNTrgHSAtM7Jqfp0_QUfjXmoQ@mail.gmail.com>
	<CAE0pAC+32rhWdBL+WbPANy0rd+eh-XsPQy-u3OHUxS0ku7eN-Q@mail.gmail.com>
	<5546682.RnG4VcateO@crushinator>
From: Marco Pontello <marcopon@gmail.com>
Date: Tue, 1 Sep 2015 23:38:58 +0200
Message-ID: <CAE0pACLQZC9Tuggwerah4LruVTfFpbOnvo0oKj4EYU8yJ9VXuQ@mail.gmail.com>
To: Matt Whitlock <bip@mattwhitlock.name>
Content-Type: multipart/alternative; boundary=001a11c3775cd28986051eb66167
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 <bitcoin-dev@lists.linuxfoundation.org>
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 <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Sep 2015 21:39:20 -0000

--001a11c3775cd28986051eb66167
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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 will 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 identify the particul=
ar
> 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<chainID> over network=3D<chainPetnameS=
tr>
> > > 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 u=
se
> > 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
>



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

--001a11c3775cd28986051eb66167
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I see your point. But I personally like that the chain par=
t could be optional, given that the vast majority of the references in the =
end will be to Bitcoin main net.</div><div class=3D"gmail_extra"><br><div c=
lass=3D"gmail_quote">On Tue, Sep 1, 2015 at 11:16 PM, Matt Whitlock <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:bip@mattwhitlock.name" target=3D"_blank">b=
ip@mattwhitlock.name</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">Isn&#39;t this all backward? The &quot;authority&quot; component of the U=
RL should identify the chain, and the &quot;path&quot; component should ide=
ntify the particular block, tx, or address in that chain.<br>
<br>
So instead of:<br>
<br>
blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f7=
6c17f?chain=3D000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce=
26f<br>
<br>
It should be:<br>
<br>
blockchain://000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce2=
6f/tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f76c17f<br>
<br>
And I would agree with allowing well-known chains to register a name, to be=
 used as an alternative to the literal, hash syntax:<br>
<br>
blockchain://bitcoin/tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24e=
cd3918f76c17f<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
On Tuesday, 1 September 2015, at 4:49 pm, Marco Pontello wrote:<br>
&gt; On Sat, Aug 29, 2015 at 10:10 PM, Jorge Tim=C3=B3n &lt;<br>
&gt; <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@l=
ists.linuxfoundation.org</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt;<br>
&gt; &gt; I would really prefer chain=3D&lt;chainID&gt; over network=3D&lt;=
chainPetnameStr&gt;<br>
&gt; &gt; By chainID I mean the hash of the genesis block, see<br>
&gt; &gt;<br>
&gt; &gt; <a href=3D"https://github.com/jtimon/bitcoin/commit/3191d5e8e7568=
7a27cf466b7a4c70bdc04809d39" rel=3D"noreferrer" target=3D"_blank">https://g=
ithub.com/jtimon/bitcoin/commit/3191d5e8e75687a27cf466b7a4c70bdc04809d39</a=
><br>
&gt; &gt; I&#39;m completely fine with doing that using an optional paramet=
er (for<br>
&gt; &gt; backwards compatibility).<br>
&gt; &gt;<br>
&gt;<br>
&gt; I see that using the genesis block hash would be the perfectly rigorou=
s way<br>
&gt; to do it, but what do you think about the possibility of letting also =
use<br>
&gt; the name constants, as a simple / more relaxed alternative? That would=
<br>
&gt; spare a source lookup just to write a correct reference to a tx, maybe=
 in a<br>
&gt; forum or a post.<br>
&gt;<br>
&gt; So a reference to a certain tx could be either:<br>
&gt;<br>
&gt; blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3=
918f76c17f<br>
&gt;<br>
&gt; blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3=
918f76c17f?chain=3D000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b6=
0a8ce26f<br>
&gt;<br>
&gt; blockchain://ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918=
f76c17f?chain=3Dmain<br>
&gt;<br>
&gt; (or a different element name maybe)<br>
&gt;<br>
&gt; --<br>
&gt; Try the Online TrID File Identifier<br>
&gt; <a href=3D"http://mark0.net/onlinetrid.aspx" rel=3D"noreferrer" target=
=3D"_blank">http://mark0.net/onlinetrid.aspx</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<div class=3D"gmail_signature">Try the Online TrID File Identifier<br><a hr=
ef=3D"http://mark0.net/onlinetrid.aspx" target=3D"_blank">http://mark0.net/=
onlinetrid.aspx</a></div>
</div>

--001a11c3775cd28986051eb66167--