From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <btcdrak@gmail.com> Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id EB5571158 for <bitcoin-dev@lists.linuxfoundation.org>; Sat, 29 Aug 2015 18:58:45 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id DED0719F for <bitcoin-dev@lists.linuxfoundation.org>; Sat, 29 Aug 2015 18:58:44 +0000 (UTC) Received: by wicne3 with SMTP id ne3so42485324wic.0 for <bitcoin-dev@lists.linuxfoundation.org>; Sat, 29 Aug 2015 11:58:43 -0700 (PDT) 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:content-transfer-encoding; bh=eUws99bm1iaZGSKzmjY8lC68fY9GqSBEVVUN4t1HAM0=; b=Eli5g9G9ilaghG3XRz23nSTniMVNphqb30fw4NCkHgTWNo9GGFPlaDKMBiAm2gf4EU LOEyCV4Dhaibr5ChUj3dPC4aHOZ7nvi0yO2RJ3GdTn/6wBHVHRNxKTqXCLNTbHZ16Z5P /5WwxGab5gFo9Qse12QSHFaGg/27qSBPumC9C4Lq7/BB3TJlTSR8eT2GBIKWlNtnv3Va DwoMAkdqi+FSca04DPVrbpb+Rvxl097NVMyiWpSJVHc3TXTUifwvZWI+nGEMgfq+51pC 7aFMKiw/cf5ECjftCRFiO3xj5MDZKZU/jT0h6G+V9I9OqC50pfzts7QXJymwkOYxsItY qFlw== X-Received: by 10.181.12.20 with SMTP id em20mr11285692wid.28.1440874723306; Sat, 29 Aug 2015 11:58:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.211.16 with HTTP; Sat, 29 Aug 2015 11:58:23 -0700 (PDT) In-Reply-To: <CF21152C-15FA-421C-B369-A9A7DB59865F@ricmoo.com> References: <CAE0pACLMcMzHkA=vEx+fiEmq7FA1bXDc4t_hQ+955=r=62V5=g@mail.gmail.com> <CF21152C-15FA-421C-B369-A9A7DB59865F@ricmoo.com> From: Btc Drak <btcdrak@gmail.com> Date: Sat, 29 Aug 2015 19:58:23 +0100 Message-ID: <CADJgMztaJHDrz0+7KLouwZMCz--Za6-2pitmjjYVHG+nJjrG=Q@mail.gmail.com> To: Richard Moore <me@ricmoo.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HK_RANDOM_ENVFROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: "bitcoin-dev@lists.linuxfoundation.org" <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: Sat, 29 Aug 2015 18:58:46 -0000 What about supporting different networks? What if I want to look up testnet for example? blockchain://mainnet/txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4= dfc3f0f7e04281a blockchain://testnet/txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4= dfc3f0f7e04281a or blockchain://txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7= e04281a blockchain://txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7= e04281a?network=3Dtestnet On Sat, Aug 29, 2015 at 5:31 PM, Richard Moore via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote: > I like the idea of having a standard for this, that all explorers (and ev= en > core, eventually) would understand. > > I would recommend 2 changes though. First, using a real URI scheme, > blockchain:// so that we can just use normal URL parsing libraries. The > bitcoin: thing leads to additional code to mutate it into a proper URI > before passing it to URL parsing. And I think it would be fine to include > the type looking up. For example: > > blockchain://blockhash/00000000000000001003e880d500968d51157f210c632e08a6= 52af3576600198 > blockchain://txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0= f7e04281a > blockchain://block/189000 > blockchain://address/1RicMooMWxqKczuRCa5D2dnJaUEn9ZJyn > > I think this would help the URI be more human understandable as well as g= ive > the explorers the ability to optimize a bit what they are looking for whe= n > hitting various databases. > > A possible future path could also include blockchain://tx/123000/4 for bl= ock > height, tx index... Another possibility could be blockchain://version whi= ch > would return a list of supported paths, version of the BIP supported, etc= . > > The BIP should also specify little endian searching. I'm not sure, but wo= uld > it also make sense for this BIP to include what the return results should > look like? Maybe another, related BIP. > > RicMoo > > Sent from my self-aware iPhone > > .=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8= =C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2= =B8=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8><(((=C2=BA> > > Richard Moore ~ Founder > Genetic Mistakes Software Inc. > phone: (778) 882-6125 > email: ricmoo@geneticmistakes.com > www: http://GeneticMistakes.com > > On Aug 29, 2015, at 7:48 AM, Marco Pontello via bitcoin-dev > <bitcoin-dev@lists.linuxfoundation.org> 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 preferre= d > 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: <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 to > distinguish blocks from txs, but in the end I think that keeping it simpl= e > 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, without having > to worry about any specific Blockchain explorer or provide a means for th= e > 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. > > > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > > > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev >