From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 5C3956C for ; 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 ; Mon, 16 Nov 2015 01:00:08 +0000 (UTC) Received: by lbbkw15 with SMTP id kw15so79835878lbb.0 for ; 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: References: From: Marco Pontello Date: Mon, 16 Nov 2015 01:59:46 +0100 Message-ID: To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= 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 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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 > 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 > 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: > >> > >> 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
Thanks for the comments! Now I fixed the typos (hope to ha= ve 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&#= 39;t need to be changed, maybe...

Now the main change wo= uld 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<= br> like its simplicity and focus. Good work!

On Sun, Nov 15, 2015 at 3:14 AM, Marco Pontello via bitcoin-dev
<bitcoin-dev@li= sts.linuxfoundation.org> wrote:
> Hi!
>
> To anyone that followed the discussion (from some time ago) about the<= br> > proposed new URI for Blockchain references / exploration, I just wante= d to
> point out that I have collected the feedback provided, reworked the te= xt,
> put the BIP on GitHub and created a pull request:
>
> https://github.com/MarcoP= on/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 looki= ng 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 specif= ic
> message was written in the Blockchain, it let you choose from 5 differ= ent
> 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 referen= ce 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.<= br> >> I had this humble idea for a while, so I thought to go ahead and p= ropose
>> 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, transa= ctions,
>> 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 th= e
>> requests for details about blocks, transactions, etc. with their p= referred
>> tool (being that a web service or a local application).
>>
>> Currently a Bitcoin client usually point to an arbitrary blockchai= n
>> 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 parti= cular
>> 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:00000000000000001003e880d500968d51157f210c632e08a652af3= 576600198
>> blockchain:001949
>>
>> blockchain:3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0= f7e04281a
>>
>> Rationale
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D
>> I thought about using some more complex scheme, or adding qualifie= rs to
>> distinguish blocks from txs, but in the end I think that keeping i= t simple
>> should be practical enough. Blockchain explorers can apply the sam= e
>> disambiguation rules they are already using to process the usual s= earch
>> box.
>>
>> From the point of view of a wallet developer (or other tool that n= eed to
>> show any kind of Blockchain references), using this scheme mean th= at 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 block= chain:
>> URI, the first time the user visit their website, or launch/instal= l 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.
>>
>>
>
>
>
> --
> Try the Online TrID File Identifier
> http://mark0.net/onlinetrid.aspx
>
> __________________= _____________________________
> bitcoin-dev mailing list
> bitcoin-dev@l= ists.linuxfoundation.org
> https://lists.linuxfoundation.org= /mailman/listinfo/bitcoin-dev
>



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