Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id E850A1304 for ; Tue, 1 Sep 2015 14:34:21 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-la0-f53.google.com (mail-la0-f53.google.com [209.85.215.53]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id F3B15259 for ; Tue, 1 Sep 2015 14:34:20 +0000 (UTC) Received: by laeb10 with SMTP id b10so1019467lae.1 for ; Tue, 01 Sep 2015 07:34:19 -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 :content-type; bh=QpS8yqwHG8Jp5rr8p/G501z6h+XP5JBO9yHomNg+mLs=; b=zyTXmSh1t1RZFHpnEiKOMX7QXLu80xnrrLueU59WD1I1Jkctbk6MpATkYKdrlkgT2z 3Z049rEGJWUyH1oB0UocpfSjkPAZdJseiZ7SBSx8cSMLRpSBZ6tvktXL+F9RUZ2PWTrT J3rp3MWPyEc2qo+RwWHteukDwFUGUQOO6ixrvV1VQY/YRvMIqSzIDoXvgMnntWB3jkh3 fQjouGI5ZJROsnWl7JfeZwQSQIL0a87uXTfa5oj5cvAuECGtN1pzblE4KNqVrrO29e9k lsJs8JGfxE0Xh+xlqJOoZEkkr55gpGkrXrhebQhwNL4fK697QAXj8b+BM4UfIGpKJ1ne vG1Q== X-Received: by 10.112.63.138 with SMTP id g10mr13485342lbs.106.1441118059257; Tue, 01 Sep 2015 07:34:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.114.186.168 with HTTP; Tue, 1 Sep 2015 07:33:59 -0700 (PDT) In-Reply-To: References: From: Marco Pontello Date: Tue, 1 Sep 2015 16:33:59 +0200 Message-ID: To: bitcoin-dev@lists.linuxfoundation.org Content-Type: multipart/alternative; boundary=001a1133d38a006551051eb07293 X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,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 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: Tue, 01 Sep 2015 14:34:22 -0000 --001a1133d38a006551051eb07293 Content-Type: text/plain; charset=UTF-8 That surely make sense. A URI like that perfectly readable, unambiguous and simple enough. And nice to see a Wallet developer showing interest for this! :) On Sat, Aug 29, 2015 at 8:07 PM, Andreas Schildbach via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > On 08/29/2015 06:31 PM, Richard Moore via bitcoin-dev wrote: > > > I like the idea of having a standard for this, that all explorers (and > > even 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/00000000000000001003e880d500968d51157f210c632e08a652af3576600198 > > > blockchain://txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a > > blockchain://block/189000 > > blockchain://address/1RicMooMWxqKczuRCa5D2dnJaUEn9ZJyn > > Good thinking! It might make sense to look at the existing de-facto > standard (e.g. blockexplorer.com, blockchain.info): > > /tx/ for transactions > /block/ for blocks, supports both hash or height > /address/ for address > > > _______________________________________________ > 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 --001a1133d38a006551051eb07293 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
That surely make sense.
A URI like that perfectly read= able, unambiguous and simple enough.

And nice to s= ee a Wallet developer showing interest for this! :)

On Sat, Aug 29, 2015 at 8:0= 7 PM, Andreas Schildbach via bitcoin-dev <bitcoin-dev@= lists.linuxfoundation.org> wrote:
On 08/29/2015 06:31 PM, Richard Moore via bitcoin-d= ev wrote:

> I like the idea of having a standard for this, that all explorers (and=
> even 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. Th= e
> 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/00000000000000001003e880d500968d51157f210c632e0= 8a652af3576600198
> blockchain://txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc= 3f0f7e04281a
> blockchain://block/189000
> blockchain://address/1RicMooMWxqKczuRCa5D2dnJaUEn9ZJyn

Good thinking! It might make sense to look at the existing de-facto<= br> standard (e.g. blockexplorer.com, blockchain.info):

/tx/ for transactions
/block/ for blocks, supports both hash or height
/address/ for address


_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.= linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev



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