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 E5B9A84 for ; Mon, 16 Nov 2015 14:43:46 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-yk0-f177.google.com (mail-yk0-f177.google.com [209.85.160.177]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id CF55C187 for ; Mon, 16 Nov 2015 14:43:45 +0000 (UTC) Received: by ykba77 with SMTP id a77so240820945ykb.2 for ; Mon, 16 Nov 2015 06:43:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jtimon_cc.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=4oCdO+uvwkUkGNydmHupChZkJDzTsOncYUVQSdk63hQ=; b=giJsy5mkAWOU0H6Hd4UKVqzD0om0pIWRQUZzCG5e77c7lMxfMMj0jsxr8mz0x9OC3g gjqZDOZoWZsvABlr7JPVTsWo9CyleJQgKKNYYV/1SE4ldpphTGoS4l8QGH0OuyNEAk7D NgvSzE63gUpJ3jy0lvkLrtaaZwFJNZJmhzxRkdI65n0fCi3pAeoYjz3ll8T3tC6TjTb0 oP89cXYKyPu4OW/IVtSlYhKKoQ/sAwkjz3nR7fJfSvyQa3JLI/gKhM052N2Jvka1+G79 4kAz2yOoK7mxsHuVxT7khqFozQkgdkQkHmY2yeI2mNsp7Vzh1RfFX/vt5Z+TsGJel9AX iJQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=4oCdO+uvwkUkGNydmHupChZkJDzTsOncYUVQSdk63hQ=; b=hMdZDPo00R45pZJfXSEgUmmcqp6rI1HjwMlv6HiDIUOarXIMUrfO0p/A2ne6Z1BHAo 8NMjA2OibqFagq/BjUzCrIH9wlcfhi2XpUqKxhs6jNog5+4vMKJaX2iDAmFT/rlh+qS1 Nns+N1bWVzBlUM3P78ccyV4hGiQpr8ZDtBS+BtlSgaIqIWjYfhqIKxqJKlaOA2XZ9uQ7 iW6V39kcBNnLDdVooZM68pJjbTBdHEdJ5t1XCh3tnnVOZGT7efZa6bxSafn1+fKZkqVG NfeuWNM3SohJ1h//4wh11LzV5hb3bhI/CfiPIE4+3U2T6gPxUe752t957M5FM1/PvMOm nc3g== X-Gm-Message-State: ALoCoQnSUvM3peGab65Gj6Ac+cpgt5EHJn/eWxyDZOgHTVsB9zwHva8mgyICmtotTtDmUrV82UQG MIME-Version: 1.0 X-Received: by 10.129.135.194 with SMTP id x185mr35864139ywf.25.1447685024916; Mon, 16 Nov 2015 06:43:44 -0800 (PST) Received: by 10.31.132.147 with HTTP; Mon, 16 Nov 2015 06:43:44 -0800 (PST) In-Reply-To: References: Date: Mon, 16 Nov 2015 15:43:44 +0100 Message-ID: From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= To: Marco Pontello Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,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 14:50:46 +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 14:43:47 -0000 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 fix= ed > the link. There probably is a better way to reference that source code pa= rt > 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 wro= te: >> >> 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 wante= d >> > 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 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 >> > 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 t= o >> > 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 particul= ar >> >> 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:00000000000000001003e880d500968d51157f210c632e08a652af3576= 600198 >> >> blockchain:001949 >> >> >> >> >> >> blockchain:3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e= 04281a >> >> >> >> 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 sear= ch >> >> 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 fo= r >> >> 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 t= he >> >> 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