MIME-Version: 1.0
From: Marco Pontello <marcopon@gmail.com>
Date: Sat, 29 Aug 2015 13:48:58 +0200
Message-ID: <CAE0pACLMcMzHkA=vEx+fiEmq7FA1bXDc4t_hQ+955=r=62V5=g@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary=001a11c25c3e531715051e71ca29
Subject: [bitcoin-dev] RFC - BIP: URI scheme for Blockchain exploration
Precedence: list

--001a11c25c3e531715051e71ca29
Content-Type: text/plain; charset=UTF-8

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.

BIP: XX
Title: URI scheme for Blockchain exploration
Author: Marco Pontello
Status: Draft
Type: Standards Track
Created: 29 August 2015

Abstract
========
This BIP propose a simple URI scheme for looking up blocks, transactions,
addresses on a Blockchain explorer.

Motivation
==========
The purpose of this URI scheme is to enable users to handle all the
requests for details about blocks, transactions, etc. with their preferred
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. 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.

Specification
=============
The URI follow this simple form:

blockchain: <hash/string>

Examples:

blockchain:00000000000000001003e880d500968d51157f210c632e08a652af3576600198
blockchain:001949
blockchain:3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a

Rationale
=========
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 simple
should be practical enough. Blockchain explorers can apply the same
disambiguation rules they are already using to process the usual search
box.

From the point of view of a wallet developer (or other tool that need to
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 the
user to select one.

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.

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.

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

<div dir=3D"ltr"><div>Hi!</div><div>My first post here, hope I&#39;m follow=
ing the right conventions.</div><div>I had this humble idea for a while, so=
 I thought to go ahead and propose</div><div>it.</div><div><br></div><div><=
div>BIP: XX</div><div>Title: URI scheme for Blockchain exploration</div><di=
v>Author: Marco Pontello</div><div>Status: Draft</div><div>Type: Standards =
Track</div><div>Created: 29 August 2015</div><div><br></div><div>Abstract</=
div><div>=3D=3D=3D=3D=3D=3D=3D=3D</div><div>This BIP propose a simple URI s=
cheme for looking up blocks, transactions,</div><div>addresses on a Blockch=
ain explorer.</div><div><br></div><div>Motivation</div><div>=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D</div><div>The purpose of this URI scheme is to enable users=
 to handle all the</div><div>requests for details about blocks, transaction=
s, etc. with their preferred</div><div>tool (being that a web service or a =
local application).</div><div><br></div><div>Currently a Bitcoin client usu=
ally point to an arbitrary blockchain</div><div>explorer when the user look=
 for the details of a transaction (es. Bitcoin</div><div>Wallet use BitEasy=
, Mycelium or Electrum use Blockchain.info, etc.).</div><div>Other times re=
sorting to cut&amp;paste is needed.</div><div>The same happens with posts a=
nd messages that reference some particular</div><div>txs or blocks, if they=
 provide links at all.</div><div><br></div><div>Specification</div><div>=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</div><div>The URI follow this simple f=
orm:</div><div><br></div><div>blockchain: &lt;hash/string&gt; =C2=A0</div><=
div><br></div><div>Examples:</div><div><br></div><div>blockchain:0000000000=
0000001003e880d500968d51157f210c632e08a652af3576600198</div><div>blockchain=
:001949</div><div>blockchain:3b95a766d7a99b87188d6875c8484cb2b310b78459b781=
6d4dfc3f0f7e04281a</div><div><br></div><div>Rationale</div><div>=3D=3D=3D=
=3D=3D=3D=3D=3D=3D</div><div>I thought about using some more complex scheme=
, or adding qualifiers to</div><div>distinguish blocks from txs, but in the=
 end I think that keeping it simple</div><div>should be practical enough. B=
lockchain explorers can apply the same</div><div>disambiguation rules they =
are already using to process the usual search</div><div>box.=C2=A0</div><di=
v><br></div><div>From the point of view of a wallet developer (or other too=
l that need to</div><div>show any kind of Blockchain references), using thi=
s scheme mean that he</div><div>can simply make it a blockchain: link and b=
e done with it, without having</div><div>to worry about any specific Blockc=
hain explorer or provide a means for the</div><div>user to select one.</div=
><div><br></div><div>Blockchain explorers in turn will simply offer to hand=
le the blockchain:</div><div>URI, the first time the user visit their websi=
te, or launch/install the</div><div>application, or even set themselves if =
there isn&#39;t already one.</div><div><br></div><div>Users get the conveni=
ence of using always their preferred explorer, which</div><div>can be espec=
ially handy on mobile devices, where juggling with cut&amp;paste</div><div>=
is far from ideal.</div><div><br></div></div><div><br></div>
</div>

--001a11c25c3e531715051e71ca29--