From: Matt Whitlock <bip@mattwhitlock.name>
To: Marco Pontello <marcopon@gmail.com>
Date: Tue, 01 Sep 2015 17:42:09 -0400
Message-ID: <1842396.ZYjkpCDfSt@crushinator>
User-Agent: KMail/4.14.10 (Linux/4.0.5-gentoo; KDE/4.14.11; x86_64; ; )
In-Reply-To: <CAE0pACLQZC9Tuggwerah4LruVTfFpbOnvo0oKj4EYU8yJ9VXuQ@mail.gmail.com>
References: <CAE0pACLMcMzHkA=vEx+fiEmq7FA1bXDc4t_hQ+955=r=62V5=g@mail.gmail.com>
	<5546682.RnG4VcateO@crushinator>
	<CAE0pACLQZC9Tuggwerah4LruVTfFpbOnvo0oKj4EYU8yJ9VXuQ@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] RFC - BIP: URI scheme for Blockchain exploration
Precedence: list

The authority part in a URI is optional.

blockchain:/tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd391=
8f76c17f

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 w=
ill be
> to Bitcoin main net.
>=20
> On Tue, Sep 1, 2015 at 11:16 PM, Matt Whitlock <bip@mattwhitlock.name=
>
> wrote:
>=20
> > Isn't this all backward? The "authority" component of the URL shoul=
d
> > identify the chain, and the "path" component should identify the pa=
rticular
> > block, tx, or address in that chain.
> >
> > So instead of:
> >
> >
> > blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24e=
cd3918f76c17f?chain=3D000000000019d6689c085ae165831e934ff763ae46a2a6c17=
2b3f1b60a8ce26f
> >
> > It should be:
> >
> >
> > blockchain://000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1=
b60a8ce26f/tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918=
f76c17f
> >
> > And I would agree with allowing well-known chains to register a nam=
e, to
> > be used as an alternative to the literal, hash syntax:
> >
> >
> > blockchain://bitcoin/tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f=
6ad2f24ecd3918f76c17f
> >
> >
> > 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:
> > >
> > > >
> > > > I would really prefer chain=3D<chainID> over network=3D<chainPe=
tnameStr>
> > > > 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=
 (for
> > > > backwards compatibility).
> > > >
> > >
> > > I see that using the genesis block hash would be the perfectly ri=
gorous
> > 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/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24e=
cd3918f76c17f
> > >
> > >
> > blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24e=
cd3918f76c17f?chain=3D000000000019d6689c085ae165831e934ff763ae46a2a6c17=
2b3f1b60a8ce26f
> > >
> > >
> > blockchain://ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3=
918f76c17f?chain=3Dmain
> > >
> > > (or a different element name maybe)
> > >
> > > --
> > > Try the Online TrID File Identifier
> > > http://mark0.net/onlinetrid.aspx
> >
>=20
>=20
>=20
> --=20
> Try the Online TrID File Identifier
> http://mark0.net/onlinetrid.aspx