path: root/96/64f6c171789ee10bb975c2396acd80e4701ec1

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 5C3956C
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 16 Nov 2015 01:00:10 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com
	[209.85.217.172])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 257EAF5
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 16 Nov 2015 01:00:08 +0000 (UTC)
Received: by lbbkw15 with SMTP id kw15so79835878lbb.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sun, 15 Nov 2015 17:00:06 -0800 (PST)
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=CcWNKjFwUlmkyi6GmWT1hsbsQRwnANUxrWAf5EzJZeU=;
	b=ZZ5/9Il2U3ZrF6DbTsS9h+nCbBn01XvO69uArakBLcqPGeRz/PYzFHJ64mf8b7sF+f
	WzzIbxiMkgTfdNY3+iDN1W3evHmJUv+vWvsBvmhG96oszZCHVpA1d4fidFYywdOKdCoS
	NDuS1BHLkYxUxYEVWIw+RHtnd8C4V5R6uwMN1f9/7kKzrZxtqf/hbvADYe3WSuCeuG86
	GELIniE6ErUXaAUNtItQbD7smOLtZBRIMHAYaZZO/DWAVrtf57JiJmI0q9FMA0cUGiwl
	IhFWUkTte26fpBc/rUJ7goh5Ul0IYbbOkWAVcWblNBqOQgcCX8fhQNDDt3hODgfmKbbQ
	yuTQ==
X-Received: by 10.112.139.164 with SMTP id qz4mr15168803lbb.78.1447635606315; 
	Sun, 15 Nov 2015 17:00:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.114.186.106 with HTTP; Sun, 15 Nov 2015 16:59:46 -0800 (PST)
In-Reply-To: <CABm2gDrutCDFAVbXAFUaAZfoHK_sKzX6ZsMpD0j=f7HJj99Zpg@mail.gmail.com>
References: <CAE0pACLMcMzHkA=vEx+fiEmq7FA1bXDc4t_hQ+955=r=62V5=g@mail.gmail.com>
	<CAE0pACLzGPHs7-KG+fzbYJzbDZ+qxkoko_uPz4Kc-1ov8jdMsA@mail.gmail.com>
	<CABm2gDrutCDFAVbXAFUaAZfoHK_sKzX6ZsMpD0j=f7HJj99Zpg@mail.gmail.com>
From: Marco Pontello <marcopon@gmail.com>
Date: Mon, 16 Nov 2015 01:59:46 +0100
Message-ID: <CAE0pACLyuaU=gJji1DkC1xkpmRjCFdRReLHa8zsD04+aDDQLeA@mail.gmail.com>
To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
Content-Type: multipart/alternative; boundary=001a11c3476e142a0205249dee22
X-Spam-Status: No, score=-1.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
	RCVD_IN_DNSWL_LOW, URIBL_BLACK autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Mon, 16 Nov 2015 01:02:03 +0000
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: Mon, 16 Nov 2015 01:00:10 -0000

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

Thanks for the comments! Now I fixed the typos (hope to have got them all,
English isn't my first language), clarified the chain part a bit, and fixed
the link. There probably is a better way to reference that source code part
with the genesis blocks hashs, in a way that doesn't need to be changed,
maybe...

Now the main change would be to put in a proper BIP number! :)

On Sun, Nov 15, 2015 at 12:42 PM, Jorge Tim=C3=B3n <jtimon@jtimon.cc> wrote=
:

> Thank you for incorporating the feedback, specifically thank you for
> using the genesis block hash as the unique chain ID.
>
> I wen't through the BIP draft and left a few of comments, but I really
> like its simplicity and focus. Good work!
>
> On Sun, Nov 15, 2015 at 3:14 AM, Marco Pontello via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
> > Hi!
> >
> > To anyone that followed the discussion (from some time ago) about the
> > proposed new URI for Blockchain references / exploration, I just wanted
> to
> > point out that I have collected the feedback provided, reworked the tex=
t,
> > put the BIP on GitHub and created a pull request:
> >
> > https://github.com/MarcoPon/bips/blob/master/bip-MarcoPon-01.mediawiki
> > https://github.com/bitcoin/bips/pull/202
> >
> > The need for an URI for this come to mind again in the last days lookin=
g
> at
> > Eternity Wall, which IMHO provide a use case that we will see more and
> more
> > in the (near) future: http://eternitywall.it/
> > Using that service, when you want to check for the proof that a specifi=
c
> > message was written in the Blockchain, it let you choose from 5 differe=
nt
> > explorer.
> > Mycelium wallet recently added the option to select one of 15 block
> > explorers.
> > And there's the crypto_bot on reddit/r/bitcoin that detect reference to
> > transaction an add a message with links to 7 different explorers.
> >
> > I think that's clearly something that's needed.
> >
> > Bye!
> >
> >
> > On Sat, Aug 29, 2015 at 1:48 PM, Marco Pontello <marcopon@gmail.com>
> 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 propo=
se
> >> 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,
> transactions,
> >> 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
> 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 particula=
r
> >> 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:00000000000000001003e880d500968d51157f210c632e08a652af35766001=
98
> >> blockchain:001949
> >>
> >>
> blockchain:3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e0428=
1a
> >>
> >> Rationale
> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D
> >> I thought about using some more complex scheme, or adding qualifiers t=
o
> >> 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 searc=
h
> >> 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 h=
e
> >> 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 blockchai=
n:
> >> URI, the first time the user visit their website, or launch/install th=
e
> >> 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&pas=
te
> >> is far from ideal.
> >>
> >>
> >
> >
> >
> > --
> > Try the Online TrID File Identifier
> > http://mark0.net/onlinetrid.aspx
> >
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev@lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> >
>



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

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

<div dir=3D"ltr">Thanks for the comments! Now I fixed the typos (hope to ha=
ve got them all, English isn&#39;t my first language), clarified the chain =
part a bit, and fixed the link. There probably is a better way to reference=
 that source code part with the genesis blocks hashs, in a way that doesn&#=
39;t need to be changed, maybe...<div><br></div><div>Now the main change wo=
uld be to put in a proper BIP number! :)</div></div><div class=3D"gmail_ext=
ra"><br><div class=3D"gmail_quote">On Sun, Nov 15, 2015 at 12:42 PM, Jorge =
Tim=C3=B3n <span dir=3D"ltr">&lt;<a href=3D"mailto:jtimon@jtimon.cc" target=
=3D"_blank">jtimon@jtimon.cc</a>&gt;</span> wrote:<br><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex">Thank you for incorporating the feedback, specifically thank you =
for<br>
using the genesis block hash as the unique chain ID.<br>
<br>
I wen&#39;t through the BIP draft and left a few of comments, but I really<=
br>
like its simplicity and focus. Good work!<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On Sun, Nov 15, 2015 at 3:14 AM, Marco Pontello via bitcoin-dev<br>
&lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@li=
sts.linuxfoundation.org</a>&gt; wrote:<br>
&gt; Hi!<br>
&gt;<br>
&gt; To anyone that followed the discussion (from some time ago) about the<=
br>
&gt; proposed new URI for Blockchain references / exploration, I just wante=
d to<br>
&gt; point out that I have collected the feedback provided, reworked the te=
xt,<br>
&gt; put the BIP on GitHub and created a pull request:<br>
&gt;<br>
&gt; <a href=3D"https://github.com/MarcoPon/bips/blob/master/bip-MarcoPon-0=
1.mediawiki" rel=3D"noreferrer" target=3D"_blank">https://github.com/MarcoP=
on/bips/blob/master/bip-MarcoPon-01.mediawiki</a><br>
&gt; <a href=3D"https://github.com/bitcoin/bips/pull/202" rel=3D"noreferrer=
" target=3D"_blank">https://github.com/bitcoin/bips/pull/202</a><br>
&gt;<br>
&gt; The need for an URI for this come to mind again in the last days looki=
ng at<br>
&gt; Eternity Wall, which IMHO provide a use case that we will see more and=
 more<br>
&gt; in the (near) future: <a href=3D"http://eternitywall.it/" rel=3D"noref=
errer" target=3D"_blank">http://eternitywall.it/</a><br>
&gt; Using that service, when you want to check for the proof that a specif=
ic<br>
&gt; message was written in the Blockchain, it let you choose from 5 differ=
ent<br>
&gt; explorer.<br>
&gt; Mycelium wallet recently added the option to select one of 15 block<br=
>
&gt; explorers.<br>
&gt; And there&#39;s the crypto_bot on reddit/r/bitcoin that detect referen=
ce to<br>
&gt; transaction an add a message with links to 7 different explorers.<br>
&gt;<br>
&gt; I think that&#39;s clearly something that&#39;s needed.<br>
&gt;<br>
&gt; Bye!<br>
&gt;<br>
&gt;<br>
&gt; On Sat, Aug 29, 2015 at 1:48 PM, Marco Pontello &lt;<a href=3D"mailto:=
marcopon@gmail.com">marcopon@gmail.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; Hi!<br>
&gt;&gt; My first post here, hope I&#39;m following the right conventions.<=
br>
&gt;&gt; I had this humble idea for a while, so I thought to go ahead and p=
ropose<br>
&gt;&gt; it.<br>
&gt;&gt;<br>
&gt;&gt; BIP: XX<br>
&gt;&gt; Title: URI scheme for Blockchain exploration<br>
&gt;&gt; Author: Marco Pontello<br>
&gt;&gt; Status: Draft<br>
&gt;&gt; Type: Standards Track<br>
&gt;&gt; Created: 29 August 2015<br>
&gt;&gt;<br>
&gt;&gt; Abstract<br>
&gt;&gt; =3D=3D=3D=3D=3D=3D=3D=3D<br>
&gt;&gt; This BIP propose a simple URI scheme for looking up blocks, transa=
ctions,<br>
&gt;&gt; addresses on a Blockchain explorer.<br>
&gt;&gt;<br>
&gt;&gt; Motivation<br>
&gt;&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
&gt;&gt; The purpose of this URI scheme is to enable users to handle all th=
e<br>
&gt;&gt; requests for details about blocks, transactions, etc. with their p=
referred<br>
&gt;&gt; tool (being that a web service or a local application).<br>
&gt;&gt;<br>
&gt;&gt; Currently a Bitcoin client usually point to an arbitrary blockchai=
n<br>
&gt;&gt; explorer when the user look for the details of a transaction (es. =
Bitcoin<br>
&gt;&gt; Wallet use BitEasy, Mycelium or Electrum use Blockchain.info, etc.=
).<br>
&gt;&gt; Other times resorting to cut&amp;paste is needed.<br>
&gt;&gt; The same happens with posts and messages that reference some parti=
cular<br>
&gt;&gt; txs or blocks, if they provide links at all.<br>
&gt;&gt;<br>
&gt;&gt; Specification<br>
&gt;&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
&gt;&gt; The URI follow this simple form:<br>
&gt;&gt;<br>
&gt;&gt; blockchain: &lt;hash/string&gt;<br>
&gt;&gt;<br>
&gt;&gt; Examples:<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; blockchain:00000000000000001003e880d500968d51157f210c632e08a652af3=
576600198<br>
&gt;&gt; blockchain:001949<br>
&gt;&gt;<br>
&gt;&gt; blockchain:3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0=
f7e04281a<br>
&gt;&gt;<br>
&gt;&gt; Rationale<br>
&gt;&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
&gt;&gt; I thought about using some more complex scheme, or adding qualifie=
rs to<br>
&gt;&gt; distinguish blocks from txs, but in the end I think that keeping i=
t simple<br>
&gt;&gt; should be practical enough. Blockchain explorers can apply the sam=
e<br>
&gt;&gt; disambiguation rules they are already using to process the usual s=
earch<br>
&gt;&gt; box.<br>
&gt;&gt;<br>
&gt;&gt; From the point of view of a wallet developer (or other tool that n=
eed to<br>
&gt;&gt; show any kind of Blockchain references), using this scheme mean th=
at he<br>
&gt;&gt; can simply make it a blockchain: link and be done with it, without=
 having<br>
&gt;&gt; to worry about any specific Blockchain explorer or provide a means=
 for the<br>
&gt;&gt; user to select one.<br>
&gt;&gt;<br>
&gt;&gt; Blockchain explorers in turn will simply offer to handle the block=
chain:<br>
&gt;&gt; URI, the first time the user visit their website, or launch/instal=
l the<br>
&gt;&gt; application, or even set themselves if there isn&#39;t already one=
.<br>
&gt;&gt;<br>
&gt;&gt; Users get the convenience of using always their preferred explorer=
, which<br>
&gt;&gt; can be especially handy on mobile devices, where juggling with cut=
&amp;paste<br>
&gt;&gt; is far from ideal.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt;<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>
&gt;<br>
</div></div><div class=3D"HOEnZb"><div class=3D"h5">&gt; __________________=
_____________________________<br>
&gt; bitcoin-dev mailing list<br>
&gt; <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@l=
ists.linuxfoundation.org</a><br>
&gt; <a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-=
dev" rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org=
/mailman/listinfo/bitcoin-dev</a><br>
&gt;<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>

--001a11c3476e142a0205249dee22--