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 555BF10F0 for ; Sat, 29 Aug 2015 19:28:21 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-ig0-f173.google.com (mail-ig0-f173.google.com [209.85.213.173]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 7B426AB for ; Sat, 29 Aug 2015 19:28:20 +0000 (UTC) Received: by igcse8 with SMTP id se8so43006925igc.1 for ; Sat, 29 Aug 2015 12:28:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ricmoo.com; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=+YTQIJpEuzqAPasEYu1qP0udL7hRw2iqCgJyMSHJQio=; b=azmug5raUPDMvjkA+Fq14joSqJy22drhMONkn1fcmHlsUzSxpl2crcxfrZb7uS4C4b PXtrr7WQRXt6JrZmAMvjqHoGSKLvYTF4pJTShAVIKpg0CPSR4hVNzZ6A/URnIBTxKJM6 rqgStyVcM/bpxWEWv1PamHem073IOyNSyZVkI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=+YTQIJpEuzqAPasEYu1qP0udL7hRw2iqCgJyMSHJQio=; b=L3kb805PddGVkWbOe3Rg+ZDXN0rhRMusxbruKRZbqlpQhXdLJvjNeZnH9JStd8G1+f inbzflnvruPlDSieaxLVbnM5o8gT5ccLWF34qOi2iJ56OmKOEtWWR+YeZ/CeTqfxvez1 DpXXY1s0vK+yciU2QOT+2jGjoRWOGOAZwsCyPqJ6OiAPGFY+MvwymtZrDPOQGir7caGu 5qRlO/ANK68omAiqz0WU2Y9wNPfuPJ/iMweQlIpukluyMObagSPxmqSdPAKG2gCh/XPZ b6AwGM8TVhPg7QzyfIglU0nbfinGGX6WvNpi6QELkt0Q0QtUxjJ/PszkHjMxCBtXJ/jt ZNEw== X-Gm-Message-State: ALoCoQk3lc9cayzqYY2gSCS67qKFe7X3IUWDum4E59wDr+bqsRhGPzmQQ07jFqNXEcWzkCIYLZFW X-Received: by 10.50.143.37 with SMTP id sb5mr392575igb.84.1440876499993; Sat, 29 Aug 2015 12:28:19 -0700 (PDT) Received: from [25.21.55.173] ([24.114.59.155]) by smtp.gmail.com with ESMTPSA id y14sm5453591iod.12.2015.08.29.12.28.18 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 29 Aug 2015 12:28:19 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) From: Richard Moore X-Mailer: iPhone Mail (12H321) In-Reply-To: Date: Sat, 29 Aug 2015 15:28:17 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <3F757B30-70CA-464F-9879-84C275DB62C7@ricmoo.com> References: To: Btc Drak X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, MIME_QP_LONG_LINE, 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" 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: Sat, 29 Aug 2015 19:28:21 -0000 Yes! Good point, network should be encoded. Not sure I like this format yet,= but what if it was part of the authority, like block:testnet. Like http use= s port 80 by default, you could have block by default refer to block:mainnet= . Eg. blockchain://tx:testnet3/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4df= c3f0f7e04281a I will read the RFC over more thoroughly tomorrow to get an idea of what typ= es of things make more or less sense. 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 2:58 PM, Btc Drak wrote: >=20 > What about supporting different networks? What if I want to look up > testnet for example? >=20 > blockchain://mainnet/txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d= 4dfc3f0f7e04281a > blockchain://testnet/txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d= 4dfc3f0f7e04281a >=20 > or >=20 > blockchain://txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f= 7e04281a > blockchain://txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f= 7e04281a?network=3Dtestnet >=20 > On Sat, Aug 29, 2015 at 5:31 PM, Richard Moore via bitcoin-dev > wrote: >> I like the idea of having a standard for this, that all explorers (and ev= en >> core, eventually) would understand. >>=20 >> 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: >>=20 >> blockchain://blockhash/00000000000000001003e880d500968d51157f210c632e08a6= 52af3576600198 >> blockchain://txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0= f7e04281a >> blockchain://block/189000 >> blockchain://address/1RicMooMWxqKczuRCa5D2dnJaUEn9ZJyn >>=20 >> 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. >>=20 >> 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= . >>=20 >> 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. >>=20 >> RicMoo >>=20 >> Sent from my self-aware iPhone >>=20 >> .=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> >>=20 >> Richard Moore ~ Founder >> Genetic Mistakes Software Inc. >> phone: (778) 882-6125 >> email: ricmoo@geneticmistakes.com >> www: http://GeneticMistakes.com >>=20 >> On Aug 29, 2015, at 7:48 AM, Marco Pontello via bitcoin-dev >> wrote: >>=20 >> 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. >>=20 >> BIP: XX >> Title: URI scheme for Blockchain exploration >> Author: Marco Pontello >> Status: Draft >> Type: Standards Track >> Created: 29 August 2015 >>=20 >> 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. >>=20 >> 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). >>=20 >> 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. >>=20 >> Specification >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> The URI follow this simple form: >>=20 >> blockchain: >>=20 >> Examples: >>=20 >> blockchain:00000000000000001003e880d500968d51157f210c632e08a652af35766001= 98 >> blockchain:001949 >> blockchain:3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e0428= 1a >>=20 >> 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. >>=20 >> =46rom the point of view of a wallet developer (or other tool that need t= o >> 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. >>=20 >> 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. >>=20 >> 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. >>=20 >>=20 >> _______________________________________________ >> bitcoin-dev mailing list >> bitcoin-dev@lists.linuxfoundation.org >> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev >>=20 >>=20 >> _______________________________________________ >> bitcoin-dev mailing list >> bitcoin-dev@lists.linuxfoundation.org >> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev >>=20