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 E3ECA71 for ; Wed, 18 Nov 2015 12:32:09 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-lb0-f180.google.com (mail-lb0-f180.google.com [209.85.217.180]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 195AB8C for ; Wed, 18 Nov 2015 12:32:08 +0000 (UTC) Received: by lbbkw15 with SMTP id kw15so23497526lbb.0 for ; Wed, 18 Nov 2015 04:32: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=OcpuhOIYYgzYWX8uNxlUs/i/jAWPChuvkwnt23M/Xxs=; b=UUmHY3iXH+z9LXbQCV5Ph8TU/MwdA1IPQu/m9VhT2pVSst6Z0HWuTnmvpI27zLKl8W B/wKBDVSbyU/lMvz1nWEB8CI568dbVIAN/XborjKlWLbTGi+X0z7IN1DA5rWPoXfXDz1 Q24cX8G2j61YmM6OKwAaUuHg4S2t4TUW954+txh47bB6aup+HDigzibIsJSuI642/K7w W8nLV/FKH8MaTJkAx5kxxejEs1qNy1JfdcyOmcZ8s/tyhG92tiOsN+N9xXcU1PM6O+pQ ZBPyfTbirvim2l/UfxC5swUOYqavosGk6Fz2Hg8Oy3dr1u3JJIWJvCH83zOABNkSatpb zpIQ== X-Received: by 10.112.14.234 with SMTP id s10mr575799lbc.136.1447849926140; Wed, 18 Nov 2015 04:32:06 -0800 (PST) MIME-Version: 1.0 Received: by 10.114.186.106 with HTTP; Wed, 18 Nov 2015 04:31:46 -0800 (PST) In-Reply-To: References: From: Marco Pontello Date: Wed, 18 Nov 2015 13:31:46 +0100 Message-ID: To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= Content-Type: multipart/alternative; boundary=001a1132fc5c892c380524cfd450 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: Wed, 18 Nov 2015 12:34: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: Wed, 18 Nov 2015 12:32:10 -0000 --001a1132fc5c892c380524cfd450 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Right, now it should be ok. Thanks. On Wed, Nov 18, 2015 at 12:29 PM, Jorge Tim=C3=B3n wrote= : > I can always link to the BIP when I reopen that commit as independent > instead of the other way around. > Btw, the PR needs rebase (probably the conflict is in the README). > > On Mon, Nov 16, 2015 at 11:10 PM, Marco Pontello > wrote: > > OK, adding the relevant code fragment is probably the simplest and dire= ct > > option. Done. > > > > On Mon, Nov 16, 2015 at 3:43 PM, Jorge Tim=C3=B3n wr= ote: > >> > >> 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 the= m > >> > all, > >> > English isn't my first language), clarified the chain part a bit, an= d > >> > fixed > >> > the link. There probably is a better way to reference that source co= de > >> > 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 fo= r > >> >> 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 t= he > >> >> > 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 mor= e > >> >> > 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 blo= ck > >> >> > 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 > >> >> >> 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 > 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, witho= ut > >> >> >> having > >> >> >> to worry about any specific Blockchain explorer or provide a mea= ns > >> >> >> 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 > > > > > > > > > > -- > > Try the Online TrID File Identifier > > http://mark0.net/onlinetrid.aspx > --=20 Try the Online TrID File Identifier http://mark0.net/onlinetrid.aspx --001a1132fc5c892c380524cfd450 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Right, now it should be ok. Thanks.

On Wed, Nov 18, 2015 at 12:29 PM, = Jorge Tim=C3=B3n <jtimon@jtimon.cc> wrote:
I can always link to the BIP when I reopen that commit as i= ndependent
instead of the other way around.
Btw, the PR needs rebase (probably the conflict is in the README).

On Mon, Nov 16, 2015 at 11:10 PM, Marco Pontello <marcopon@gmail.com> wrote:
> OK, adding the relevant code fragment is probably the simplest and dir= ect
> option. Done.
>
> On Mon, Nov 16, 2015 at 3:43 PM, Jorge Tim=C3=B3n <jtimon@jtimon.cc= > wrote:
>>
>> Not a native english speaker myself, so I may have missed some thi= ngs...
>>
>> Yes, sorry about the link. I guess you can point to #6230 . I can<= br> >> 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 lea= st
>> 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 #638= 2 is
>> certainly going to need rebase and the link will be broken again.<= br> >> 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 (whic= h
>> 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 par= t a bit, and
>> > fixed
>> > the link. There probably is a better way to reference that so= urce 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 th= ank you for
>> >> using the genesis block hash as the unique chain ID.
>> >>
>> >> I wen't through the BIP draft and left a few of comme= nts, but I really
>> >> like its simplicity and focus. Good work!
>> >>
>> >> On Sun, Nov 15, 2015 at 3:14 AM, Marco Pontello via bitco= in-dev
>> >> <bitcoin-dev@lists.linuxfoundation.org> wrote:
>> >> > Hi!
>> >> >
>> >> > To anyone that followed the discussion (from some ti= me ago) about the
>> >> > proposed new URI for Blockchain references / explora= tion, I just
>> >> > wanted
>> >> > to
>> >> > point out that I have collected the feedback provide= d, 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 t= he last days
>> >> > 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 p= roof that a
>> >> > specific
>> >> > message was written in the Blockchain, it let you ch= oose 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 t= hat detect reference
>> >> > to
>> >> > transaction an add a message with links to 7 differe= nt explorers.
>> >> >
>> >> > I think that's clearly something that's need= ed.
>> >> >
>> >> > 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 r= ight 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 user= s to handle all the
>> >> >> requests for details about blocks, transactions,= etc. with their
>> >> >> preferred
>> >> >> tool (being that a web service or a local applic= ation).
>> >> >>
>> >> >> Currently a Bitcoin client usually point to an a= rbitrary blockchain
>> >> >> explorer when the user look for the details of a= transaction (es.
>> >> >> Bitcoin
>> >> >> Wallet use BitEasy, Mycelium or Electrum use Blo= ckchain.info, etc.).
>> >> >> Other times resorting to cut&paste is needed= .
>> >> >> The same happens with posts and messages that re= ference 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: <hash/string>
>> >> >>
>> >> >> Examples:
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> blockchain:00000000000000001003e880d500968d51157= f210c632e08a652af3576600198
>> >> >> blockchain:001949
>> >> >>
>> >> >>
>> >> >>
>> >> >> blockchain:3b95a766d7a99b87188d6875c8484cb2b310b= 78459b7816d4dfc3f0f7e04281a
>> >> >>
>> >> >> 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 th= ink that keeping it
>> >> >> simple
>> >> >> should be practical enough. Blockchain explorers= can apply the same
>> >> >> disambiguation rules they are already using to p= rocess 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 t= his scheme mean that
>> >> >> he
>> >> >> can simply make it a blockchain: link and be don= e 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 t= o 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.l= inuxfoundation.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



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