Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id C0B6883 for ; Sun, 15 Nov 2015 11:42:35 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-vk0-f44.google.com (mail-vk0-f44.google.com [209.85.213.44]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id D246613D for ; Sun, 15 Nov 2015 11:42:34 +0000 (UTC) Received: by vkas68 with SMTP id s68so14561534vka.2 for ; Sun, 15 Nov 2015 03:42:34 -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; bh=L96sBkBY9MS2R/87VqZpMgZqdFqaWetyQ+gZP2iIWrQ=; b=Tx6C1duOTEoPOSKmUz8ogv6xxUc8Wz5cPGNBRWQmNGpoqYaD91yCF9AB+Bj5II88j/ R+Joo3+IduH+btSAyziZEjTcpSE2ofauk772EkQuCH9+mIPWUm+KzmETTJyHKS4fY2IZ bCh9ySHEzXIm3ZKiyRKcQ5Q9fZpcsoHu43VXnZEMNOwgJEinAjLamLTFnK4zqmk5+35E WZXQZvM5MaAkrVfHmIRhhxRCtEuUHkzUgR1SPMouztTrJaYPdRDRr3lvYH7wkNe9ks8R peWzrhbi1Su+9oDPi+uWzT+8EZoxaA/w6JnTKV776Db80fh13cmIozi3kho8I/2fkrxs PiRQ== 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; bh=L96sBkBY9MS2R/87VqZpMgZqdFqaWetyQ+gZP2iIWrQ=; b=NAN2T7BjtRPOjnoPKNeTdc6v8NXYdIC9+t0M8fl9GjNmzUSNmoyZ8ga74w866CqNRe MhdkK2VBdVmPeuHXPvlJ8L1wLTnQlr5dIw8OTHzW9nqeO7iSfZOZByNIUllueyfgQP1/ kAitFupL3FFvCW4RO26DGuqs+hez1NeV0GDFitM/TylFEUbV9nYT43coBUDqOtHEwow5 ypGmwExCY4G2FBJf71rurWlrEj0CPfh+o49IXJtJ+f/fhxGXaFDQgKcT2gJo1fwgaqZu HTX94gkdFvXMVBbrhKkoZAWWKScAGSwoNAwiZwoZ5WpiTpc/FJ1kf4xuuUy19xghudkk EV5g== X-Gm-Message-State: ALoCoQn2WgGDWVL76nIhDnBcrvbLwV92Qbh+spQ4N89UZo2UrCIrS4MC9S8PIzkx+Mwl26zVlapt MIME-Version: 1.0 X-Received: by 10.31.7.202 with SMTP id 193mr7375226vkh.46.1447587754063; Sun, 15 Nov 2015 03:42:34 -0800 (PST) Received: by 10.31.132.147 with HTTP; Sun, 15 Nov 2015 03:42:33 -0800 (PST) In-Reply-To: References: Date: Sun, 15 Nov 2015 12:42:33 +0100 Message-ID: From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= To: Marco Pontello Content-Type: text/plain; charset=UTF-8 X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,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 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: Sun, 15 Nov 2015 11:42:35 -0000 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 wanted 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 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 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 block > 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 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 >> ======== >> This BIP propose a simple URI scheme for looking up blocks, transactions, >> addresses on a Blockchain explorer. >> >> Motivation >> ========== >> 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 >> ============= >> The URI follow this simple form: >> >> blockchain: >> >> Examples: >> >> >> blockchain:00000000000000001003e880d500968d51157f210c632e08a652af3576600198 >> blockchain:001949 >> >> blockchain:3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a >> >> Rationale >> ========= >> 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, 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 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 >