Subject: Re: [bitcoin-dev] RFC - BIP: URI scheme for Blockchain exploration

From: Marco Pontello <[email-masked]>
Date: Tue, 1 Sep 2015 16:49:47 +0200

On Sat, Aug 29, 2015 at 10:10 PM, Jorge Timón <
[email-masked]> wrote:

>
> I would really prefer chain=<chainID> over network=<chainPetnameStr>
> By chainID I mean the hash of the genesis block, see
>
> https://github.com/jtimon/bitcoin/commit/3191d5e8e75687a27cf466b7a4c70bdc04809d39
> I'm completely fine with doing that using an optional parameter (for
> backwards compatibility).
>

I see that using the genesis block hash would be the perfectly rigorous way
to do it, but what do you think about the possibility of letting also use
the name constants, as a simple / more relaxed alternative? That would
spare a source lookup just to write a correct reference to a tx, maybe in a
forum or a post.

So a reference to a certain tx could be either:

blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f76c17f

blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f76c17f?chain=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f

blockchain://ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f76c17f?chain=main

(or a different element name maybe)

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