Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (1.0)
From: Richard Moore <me@ricmoo.com>
In-Reply-To: <CADJgMztaJHDrz0+7KLouwZMCz--Za6-2pitmjjYVHG+nJjrG=Q@mail.gmail.com>
Date: Sat, 29 Aug 2015 15:28:17 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3F757B30-70CA-464F-9879-84C275DB62C7@ricmoo.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>
To: Btc Drak <btcdrak@gmail.com>
Cc: "bitcoin-dev@lists.linuxfoundation.org"
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] RFC - BIP: URI scheme for Blockchain exploration
Precedence: list

Yes! Good point, network should be encoded. Not sure I like this format yet,=
 but what if it was part of the authority, like block:testnet. Like http use=
s port 80 by default, you could have block by default refer to block:mainnet=
.

Eg.
blockchain://tx:testnet3/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4df=
c3f0f7e04281a

I will read the RFC over more thoroughly tomorrow to get an idea of what typ=
es of things make more or less sense.

RicMoo

Sent from my self-aware iPhone

.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=C2=B8=
.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=C2=B8=
.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8><(((=C2=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 2:58 PM, Btc Drak <btcdrak@gmail.com> wrote:
>=20
> What about supporting different networks? What if I want to look up
> testnet for example?
>=20
> blockchain://mainnet/txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d=
4dfc3f0f7e04281a
> blockchain://testnet/txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d=
4dfc3f0f7e04281a
>=20
> or
>=20
> blockchain://txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f=
7e04281a
> blockchain://txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f=
7e04281a?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 ev=
en
>> core, eventually) would understand.
>>=20
>> 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 include=

>> the type looking up. For example:
>>=20
>> blockchain://blockhash/00000000000000001003e880d500968d51157f210c632e08a6=
52af3576600198
>> blockchain://txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0=
f7e04281a
>> blockchain://block/189000
>> blockchain://address/1RicMooMWxqKczuRCa5D2dnJaUEn9ZJyn
>>=20
>> I think this would help the URI be more human understandable as well as g=
ive
>> the explorers the ability to optimize a bit what they are looking for whe=
n
>> hitting various databases.
>>=20
>> A possible future path could also include blockchain://tx/123000/4 for bl=
ock
>> height, tx index... Another possibility could be blockchain://version whi=
ch
>> would return a list of supported paths, version of the BIP supported, etc=
.
>>=20
>> The BIP should also specify little endian searching. I'm not sure, but wo=
uld
>> it also make sense for this BIP to include what the return results should=

>> look like? Maybe another, related BIP.
>>=20
>> RicMoo
>>=20
>> Sent from my self-aware iPhone
>>=20
>> .=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=C2=
=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=C2=
=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8><(((=C2=BA>
>>=20
>> Richard Moore ~ Founder
>> Genetic Mistakes Software Inc.
>> phone: (778) 882-6125
>> email: ricmoo@geneticmistakes.com
>> www: http://GeneticMistakes.com
>>=20
>> On Aug 29, 2015, at 7:48 AM, Marco Pontello via bitcoin-dev
>> <bitcoin-dev@lists.linuxfoundation.org> wrote:
>>=20
>> 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 propose
>> it.
>>=20
>> BIP: XX
>> Title: URI scheme for Blockchain exploration
>> Author: Marco Pontello
>> Status: Draft
>> Type: Standards Track
>> Created: 29 August 2015
>>=20
>> Abstract
>> =3D=3D=3D=3D=3D=3D=3D=3D
>> This BIP propose a simple URI scheme for looking up blocks, transactions,=

>> addresses on a Blockchain explorer.
>>=20
>> 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 preferre=
d
>> tool (being that a web service or a local application).
>>=20
>> Currently a Bitcoin client usually point to an arbitrary blockchain
>> explorer when the user look for the details of a transaction (es. Bitcoin=

>> 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 particular
>> txs or blocks, if they provide links at all.
>>=20
>> Specification
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> The URI follow this simple form:
>>=20
>> blockchain: <hash/string>
>>=20
>> Examples:
>>=20
>> blockchain:00000000000000001003e880d500968d51157f210c632e08a652af35766001=
98
>> blockchain:001949
>> blockchain:3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e0428=
1a
>>=20
>> Rationale
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D
>> I thought about using some more complex scheme, or adding qualifiers to
>> distinguish blocks from txs, but in the end I think that keeping it simpl=
e
>> should be practical enough. Blockchain explorers can apply the same
>> disambiguation rules they are already using to process the usual search
>> box.
>>=20
>> =46rom the point of view of a wallet developer (or other tool that need t=
o
>> show any kind of Blockchain references), using this scheme mean that 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 th=
e
>> user to select one.
>>=20
>> Blockchain explorers in turn will simply offer to handle the blockchain:
>> URI, the first time the user visit their website, or launch/install the
>> application, or even set themselves if there isn't already one.
>>=20
>> 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.
>>=20
>>=20
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>=20
>>=20
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>=20