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 300D574 for ; Mon, 16 Nov 2015 22:11:12 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-lf0-f43.google.com (mail-lf0-f43.google.com [209.85.215.43]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id B2385138 for ; Mon, 16 Nov 2015 22:11:10 +0000 (UTC) Received: by lffu14 with SMTP id u14so95638463lff.1 for ; Mon, 16 Nov 2015 14:11:08 -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=NK3Ew9j0OK8nllCLMkLVIXaBihHrS31qSCdw08jLyds=; b=A6QMMDkPEpr4PrD5m5aPj4pizNdyx+MffeI2C2BBNHKMoWrbgfSfI1WCRE3jJ8MvGF 88p6BHGlPU0oGumpSeBXHlZuuoxCZ+Y0x+/0BOGIDwUWhh6uX40SU/u8x8coU4F2lpqA YoPkwNDtBdihfn9rDVOPP04NVaYRcNeTTe/s5MqmxPqTcP+gNTkjb5O4QvoOqyeoNt76 x937ASZOJrCi/pXCNeubU4z/dPekCz2F4Wr8zifpZAz0/YlM5YVuHaZ36dOqYM8gSVcy sIpSQnn9XMypjAap7EY+yeveZA1RSO1smXz7yj/7EmHwmy7DUFvJ8VG6dS3Bdlxg9ohX VRow== X-Received: by 10.25.8.7 with SMTP id 7mr18278995lfi.52.1447711868739; Mon, 16 Nov 2015 14:11:08 -0800 (PST) MIME-Version: 1.0 Received: by 10.114.186.106 with HTTP; Mon, 16 Nov 2015 14:10:49 -0800 (PST) In-Reply-To: References: From: Marco Pontello Date: Mon, 16 Nov 2015 23:10:49 +0100 Message-ID: To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= Content-Type: multipart/alternative; boundary=001a113ebb8cac68100524afaf0b 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 22:37:00 +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 22:11:12 -0000 --001a113ebb8cac68100524afaf0b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable OK, adding the relevant code fragment is probably the simplest and direct option. Done. On Mon, Nov 16, 2015 at 3:43 PM, Jorge Tim=C3=B3n wrote: > Not a native english speaker myself, so I may have missed some things... > > Yes, sorry about the link. I guess you can point to #6230 . I can > rebase it if needed but I would close it again because I don't want to > have too many things from #6382 opened at the same time (is noisy and > worse for review). My plan was to not open it independently at least > until after #6907 (and actually after 0.12 assuming #6907 gets in by > 0.12). But then I would maybe open a new one and reference the old one > rather than reopening #6230 (which tends to be confusing). > I'm not really sure what's the best answer here...but #6382 is > certainly going to need rebase and the link will be broken again. > Maybe one answer is to copy some text from #6230 or the commit and add > it directly to the BIP instead of referencing to that commit (which > will be, at least until #6907 is merged, a moving target). > > On Mon, Nov 16, 2015 at 1:59 AM, Marco Pontello > wrote: > > 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 w= rote: > >> > >> 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 th= e > >> > proposed new URI for Blockchain references / exploration, I just > wanted > >> > to > >> > point out that I have collected the feedback provided, reworked the > >> > text, > >> > 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 > looking > >> > at > >> > Eternity Wall, which IMHO provide a use case that we will see more a= nd > >> > more > >> > in the (near) future: http://eternitywall.it/ > >> > Using that service, when you want to check for the proof that a > specific > >> > message was written in the Blockchain, it let you choose from 5 > >> > different > >> > 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 > >> >> propose > >> >> 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 > particular > >> >> 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 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 > search > >> >> 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 > >> >> 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. > >> >> > >> >> > >> > > >> > > >> > > >> > -- > >> > 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 > >> > > > > > > > > > > > -- > > Try the Online TrID File Identifier > > http://mark0.net/onlinetrid.aspx > --=20 Try the Online TrID File Identifier http://mark0.net/onlinetrid.aspx --001a113ebb8cac68100524afaf0b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
OK, adding the relevant code fragment is probably the simp= lest and direct option. Done.

On Mon, Nov 16, 2015 at 3:43 PM, Jorge Tim=C3=B3n <jtimon= @jtimon.cc> wrote:
Not a na= tive english speaker myself, so I may have missed some things...

Yes, sorry about the link. I guess you can point to #6230 . I can
rebase it if needed but I would close it again because I don't want to<= br> have too many things from #6382 opened at the same time (is noisy and
worse for review). My plan was to not open it independently at least
until after #6907 (and actually after 0.12 assuming #6907 gets in by
0.12). But then I would maybe open a new one and reference the old one
rather than reopening #6230 (which tends to be confusing).
I'm not really sure what's the best answer here...but #6382 is
certainly going to need rebase and the link will be broken again.
Maybe one answer is to copy some text from #6230 or the commit and add
it directly to the BIP instead of referencing to that commit (which
will be, at least until #6907 is merged, a moving target).

On Mon, Nov 16, 2015 at 1:59 AM, Marco Pontello <marcopon@gmail.com> wrote:
> 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 ch= anged,
> 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.c= c> wrote:
>>
>> Thank you for incorporating the feedback, specifically thank you f= or
>> 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 >> <bitco= in-dev@lists.linuxfoundation.org> wrote:
>> > Hi!
>> >
>> > To anyone that followed the discussion (from some time ago) a= bout the
>> > proposed new URI for Blockchain references / exploration, I j= ust wanted
>> > to
>> > point out that I have collected the feedback provided, rework= ed the
>> > text,
>> > put the BIP on GitHub and created a pull request:
>> >
>> > https://github.c= om/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 d= ays looking
>> > 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 specific
>> > message was written in the Blockchain, it let you choose from= 5
>> > different
>> > 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 detec= t reference to
>> > transaction an add a message with links to 7 different explor= ers.
>> >
>> > 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 conv= entions.
>> >> I had this humble idea for a while, so I thought to go ah= ead and
>> >> propose
>> >> 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 block= s,
>> >> 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 hand= le all the
>> >> requests for details about blocks, transactions, etc. wit= h 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 transact= ion (es.
>> >> Bitcoin
>> >> Wallet use BitEasy, Mycelium or Electrum use Blockchain.i= nfo, etc.).
>> >> Other times resorting to cut&paste is needed.
>> >> The same happens with posts and messages that reference s= ome particular
>> >> 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:00000000000000001003e880d500968d51157f210c632e= 08a652af3576600198
>> >> blockchain:001949
>> >>
>> >>
>> >> blockchain:3b95a766d7a99b87188d6875c8484cb2b310b78459b781= 6d4dfc3f0f7e04281a
>> >>
>> >> 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
>> >> simple
>> >> should be practical enough. Blockchain explorers can appl= y the same
>> >> disambiguation rules they are already using to process th= e usual search
>> >> box.
>> >>
>> >> From the point of view of a wallet developer (or other to= ol that need
>> >> to
>> >> show any kind of Blockchain references), using this schem= e 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 provid= e 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 laun= ch/install the
>> >> application, or even set themselves if there isn't al= ready 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
>> > bitc= oin-dev@lists.linuxfoundation.org
>> > https://lists.linuxfound= ation.org/mailman/listinfo/bitcoin-dev
>> >
>
>
>
>
> --
> Try the Online TrID File Identifier
> http://mark0.net/onlinetrid.aspx



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