summaryrefslogtreecommitdiff
path: root/08/f093f49b4dd0fddf15eb0b2ccdb624c9c6814f
blob: a2289474d9d74a0c1d491d09a55a7ccbe8b4ef8c (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
Return-Path: <jtimon@jtimon.cc>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 069861172
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 29 Aug 2015 20:10:51 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-lb0-f175.google.com (mail-lb0-f175.google.com
	[209.85.217.175])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 445041E5
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 29 Aug 2015 20:10:50 +0000 (UTC)
Received: by lbbtg9 with SMTP id tg9so44981570lbb.1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 29 Aug 2015 13:10:48 -0700 (PDT)
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=j+VWZ+H5kcgFdHb8QTAg8GJnI1TOE0GmMXJV3VaEpT8=;
	b=G75//hBQC38C9eMAYFkGdvvzcOILweuZQrmMEcTfRkNlAPSIWYpIU1mHuNQ5tozZfq
	xukPsvwnxMMvVzJxgDgd3mdLJT6FsEK39I8l881/DLyCovT1IxNHx85o1D7Y8li8BEuh
	xc8SVTMpL0uAiL0C7/G+TXuGniOMQBAy4OjnvSsZ4J4QycqLj+An+bu8Uc2F/TTQjCRU
	AjXjzAV6SRKxcQ91Pi3hNZuL+wADpXOkXTZz9HdnVEgTyl+d6XCDOp6HFE48AyxuiBnM
	0G0T7wrv09cuGmy7o2YTiALi6HE3d3agBJrFIPrQLk783QLp1xK6wxtvt8Ii/F8HMPeM
	ypyA==
X-Gm-Message-State: ALoCoQk/Kn/046GPAAwn+Zk9hm2dPLVuG/+MvemmlFj69mK8fA82S8oblKQaoYqbmesbWinU2gmy
MIME-Version: 1.0
X-Received: by 10.153.4.39 with SMTP id cb7mr703148lad.22.1440879048195; Sat,
	29 Aug 2015 13:10:48 -0700 (PDT)
Received: by 10.25.15.22 with HTTP; Sat, 29 Aug 2015 13:10:48 -0700 (PDT)
In-Reply-To: <2509151.XgrrNGsCxR@crushinator>
References: <CAE0pACLMcMzHkA=vEx+fiEmq7FA1bXDc4t_hQ+955=r=62V5=g@mail.gmail.com>
	<CF21152C-15FA-421C-B369-A9A7DB59865F@ricmoo.com>
	<CADJgMztaJHDrz0+7KLouwZMCz--Za6-2pitmjjYVHG+nJjrG=Q@mail.gmail.com>
	<2509151.XgrrNGsCxR@crushinator>
Date: Sat, 29 Aug 2015 22:10:48 +0200
Message-ID: <CABm2gDpC55dsr4GNAUabgnOeXcNTrgHSAtM7Jqfp0_QUfjXmoQ@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Matt Whitlock <bip@mattwhitlock.name>
Content-Type: text/plain; charset=UTF-8
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,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 <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 20:10:51 -0000

On Sat, Aug 29, 2015 at 9:01 PM, Matt Whitlock via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> That's still not right, since "mainnet" and "testnet" are not host names.
>
> You'd have to do something like:
>
> blockchain:?network=testnet&txid=3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a

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 agree with Andreas Schildbach that respecting the most commonly used
schemes is desirable.
So my preference would be:

/tx/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a?chain=000000000933ea01ad0ee984209779baaec3ced90fa3f408719526f8d77f4943

(a tx in testnet)

/block/00000000000000000b0d504d142ac8bdd1a2721d19f423a8146d0d6de882167b?chain=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f

(a block in bitcoin's mainnet)