From: Matt Whitlock <bip@mattwhitlock.name>
To: bitcoin-dev@lists.linuxfoundation.org, Btc Drak <btcdrak@gmail.com>
Date: Sat, 29 Aug 2015 15:01:23 -0400
Message-ID: <2509151.XgrrNGsCxR@crushinator>
User-Agent: KMail/4.14.10 (Linux/4.0.5-gentoo; KDE/4.14.11; x86_64; ; )
In-Reply-To: <CADJgMztaJHDrz0+7KLouwZMCz--Za6-2pitmjjYVHG+nJjrG=Q@mail.gmail.com>
References: <CAE0pACLMcMzHkA=vEx+fiEmq7FA1bXDc4t_hQ+955=r=62V5=g@mail.gmail.com>
	<CF21152C-15FA-421C-B369-A9A7DB59865F@ricmoo.com>
	<CADJgMztaJHDrz0+7KLouwZMCz--Za6-2pitmjjYVHG+nJjrG=Q@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
Subject: Re: [bitcoin-dev] RFC - BIP: URI scheme for Blockchain exploration
Precedence: list

That's still not right, since "mainnet" and "testnet" are not host name=
s.

You'd have to do something like:

blockchain:?network=3Dtestnet&txid=3D3b95a766d7a99b87188d6875c8484cb2b3=
10b78459b7816d4dfc3f0f7e04281a


On Saturday, 29 August 2015, at 7:58 pm, Btc Drak via bitcoin-dev wrote=
:
> What about supporting different networks? What if I want to look up
> testnet for example?
>=20
> blockchain://mainnet/txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b=
7816d4dfc3f0f7e04281a
> blockchain://testnet/txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b=
7816d4dfc3f0f7e04281a
>=20
> or
>=20
> blockchain://txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4df=
c3f0f7e04281a
> blockchain://txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4df=
c3f0f7e04281a?network=3Dtestnet
>=20
> On Sat, Aug 29, 2015 at 5:31 PM, Richard Moore via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
> > I like the idea of having a standard for this, that all explorers (=
and even
> > core, eventually) would understand.
> >
> > I would recommend 2 changes though. First, using a real URI scheme,=

> > blockchain:// so that we can just use normal URL parsing libraries.=
 The
> > bitcoin: thing leads to additional code to mutate it into a proper =
URI
> > before passing it to URL parsing. And I think it would be fine to i=
nclude
> > the type looking up. For example:
> >
> > blockchain://blockhash/00000000000000001003e880d500968d51157f210c63=
2e08a652af3576600198
> > blockchain://txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4=
dfc3f0f7e04281a
> > blockchain://block/189000
> > blockchain://address/1RicMooMWxqKczuRCa5D2dnJaUEn9ZJyn
> >
> > I think this would help the URI be more human understandable as wel=
l as give
> > the explorers the ability to optimize a bit what they are looking f=
or when
> > hitting various databases.
> >
> > A possible future path could also include blockchain://tx/123000/4 =
for block
> > height, tx index... Another possibility could be blockchain://versi=
on which
> > would return a list of supported paths, version of the BIP supporte=
d, etc.
> >
> > The BIP should also specify little endian searching. I'm not sure, =
but would
> > it also make sense for this BIP to include what the return results =
should
> > look like? Maybe another, related BIP.
> >
> > RicMoo
> >
> > Sent from my self-aware iPhone
> >
> > .=B7=B4=AF`=B7.=B8=B8.=B7=B4=AF`=B7.=B8=B8.=B7=B4=AF`=B7.=B8=B8.=B7=
=B4=AF`=B7.=B8=B8.=B7=B4=AF`=B7.=B8><(((=BA>
> >
> > Richard Moore ~ Founder
> > Genetic Mistakes Software Inc.
> > phone: (778) 882-6125
> > email: ricmoo@geneticmistakes.com
> > www: http://GeneticMistakes.com
> >
> > On Aug 29, 2015, at 7:48 AM, Marco Pontello via bitcoin-dev
> > <bitcoin-dev@lists.linuxfoundation.org> wrote:
> >
> > Hi!
> > My first post here, hope I'm following the right conventions.
> > I had this humble idea for a while, so I thought to go ahead and pr=
opose
> > it.
> >
> > BIP: XX
> > Title: URI scheme for Blockchain exploration
> > Author: Marco Pontello
> > Status: Draft
> > Type: Standards Track
> > Created: 29 August 2015
> >
> > Abstract
> > =3D=3D=3D=3D=3D=3D=3D=3D
> > This BIP propose a simple URI scheme for looking up blocks, transac=
tions,
> > addresses on a Blockchain explorer.
> >
> > Motivation
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > The purpose of this URI scheme is to enable users to handle all the=

> > requests for details about blocks, transactions, etc. with their pr=
eferred
> > tool (being that a web service or a local application).
> >
> > Currently a Bitcoin client usually point to an arbitrary blockchain=

> > explorer when the user look for the details of a transaction (es. B=
itcoin
> > Wallet use BitEasy, Mycelium or Electrum use Blockchain.info, etc.)=
.
> > Other times resorting to cut&paste is needed.
> > The same happens with posts and messages that reference some partic=
ular
> > txs or blocks, if they provide links at all.
> >
> > Specification
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > The URI follow this simple form:
> >
> > blockchain: <hash/string>
> >
> > Examples:
> >
> > blockchain:00000000000000001003e880d500968d51157f210c632e08a652af35=
76600198
> > blockchain:001949
> > blockchain:3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f=
7e04281a
> >
> > Rationale
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D
> > I thought about using some more complex scheme, or adding qualifier=
s to
> > distinguish blocks from txs, but in the end I think that keeping it=
 simple
> > should be practical enough. Blockchain explorers can apply the same=

> > disambiguation rules they are already using to process the usual se=
arch
> > box.
> >
> > From the point of view of a wallet developer (or other tool that ne=
ed to
> > show any kind of Blockchain references), using this scheme mean tha=
t he
> > can simply make it a blockchain: link and be done with it, without =
having
> > to worry about any specific Blockchain explorer or provide a means =
for the
> > user to select one.
> >
> > Blockchain explorers in turn will simply offer to handle the blockc=
hain:
> > URI, the first time the user visit their website, or launch/install=
 the
> > application, or even set themselves if there isn't already one.
> >
> > Users get the convenience of using always their preferred explorer,=
 which
> > can be especially handy on mobile devices, where juggling with cut&=
paste
> > is far from ideal.
> >
> >
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev@lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> >
> >
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev@lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> >
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev