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
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
|
Return-Path: <bip@mattwhitlock.name>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 4A1C212B3
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 21:16:40 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from resqmta-po-10v.sys.comcast.net (resqmta-po-10v.sys.comcast.net
[96.114.154.169])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 8EDA61A9
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 21:16:39 +0000 (UTC)
Received: from resomta-po-06v.sys.comcast.net ([96.114.154.230])
by resqmta-po-10v.sys.comcast.net with comcast
id BxGY1r0044yXVJQ01xGeQX; Tue, 01 Sep 2015 21:16:38 +0000
Received: from crushinator.localnet
([IPv6:2601:186:c000:825e:e9f4:8901:87c7:24a0])
by resomta-po-06v.sys.comcast.net with comcast
id BxGd1r00J4eLRLv01xGemA; Tue, 01 Sep 2015 21:16:38 +0000
From: Matt Whitlock <bip@mattwhitlock.name>
To: Marco Pontello <marcopon@gmail.com>
Date: Tue, 01 Sep 2015 17:16:37 -0400
Message-ID: <5546682.RnG4VcateO@crushinator>
User-Agent: KMail/4.14.10 (Linux/4.0.5-gentoo; KDE/4.14.11; x86_64; ; )
In-Reply-To: <CAE0pAC+32rhWdBL+WbPANy0rd+eh-XsPQy-u3OHUxS0ku7eN-Q@mail.gmail.com>
References: <CAE0pACLMcMzHkA=vEx+fiEmq7FA1bXDc4t_hQ+955=r=62V5=g@mail.gmail.com>
<CABm2gDpC55dsr4GNAUabgnOeXcNTrgHSAtM7Jqfp0_QUfjXmoQ@mail.gmail.com>
<CAE0pAC+32rhWdBL+WbPANy0rd+eh-XsPQy-u3OHUxS0ku7eN-Q@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net;
s=q20140121; t=1441142198;
bh=+ltiXrAEvCC8Uu9dReFlTs16XP0NALPqij4LvCIYHCY=;
h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version:
Content-Type;
b=bVMtYbo6wMpW3CJBNVV8myux4Be0g8H1RtCxyex00Mc7I7PXvhDu+uwt8UANDwqBt
gatxL/JAW7IXFpL7CNc56qIJjuuMC+5xewA0T8Iv5zlUGBq+dl4d5jzT/v5V+QqLk3
U5Hs8ItCBntKf0c1kHoQEDzu+37ymZFcFoI1KcbjFUVNGDJaRx/PJln16knBnk1B1n
SE8O7K3JwdxPKiTlwefEp5Bt4kbkw/n+5Ut8tv2SquBlBDz29TbEgLgNnMattPd2mg
NEVHLh7G1sXmCS2nK2d1U7QbioZWgIzCX8p+UJD1ePtcIVg14d+8ToFWqlMa2dCuzI
2jsn6c5bz8CCw==
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,RCVD_IN_DNSWL_NONE 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: Tue, 01 Sep 2015 21:16:40 -0000
Isn't this all backward? The "authority" component of the URL should id=
entify the chain, and the "path" component should identify the particul=
ar block, tx, or address in that chain.
So instead of:
blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd39=
18f76c17f?chain=3D000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f=
1b60a8ce26f
It should be:
blockchain://000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a=
8ce26f/tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f76c=
17f
And I would agree with allowing well-known chains to register a name, t=
o be used as an alternative to the literal, hash syntax:
blockchain://bitcoin/tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2=
f24ecd3918f76c17f
On Tuesday, 1 September 2015, at 4:49 pm, Marco Pontello wrote:
> On Sat, Aug 29, 2015 at 10:10 PM, Jorge Tim=F3n <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>=20
> >
> > I would really prefer chain=3D<chainID> over network=3D<chainPetnam=
eStr>
> > By chainID I mean the hash of the genesis block, see
> >
> > https://github.com/jtimon/bitcoin/commit/3191d5e8e75687a27cf466b7a4=
c70bdc04809d39
> > I'm completely fine with doing that using an optional parameter (fo=
r
> > backwards compatibility).
> >
>=20
> I see that using the genesis block hash would be the perfectly rigoro=
us 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 woul=
d
> spare a source lookup just to write a correct reference to a tx, mayb=
e in a
> forum or a post.
>=20
> So a reference to a certain tx could be either:
>=20
> blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd=
3918f76c17f
>=20
> blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd=
3918f76c17f?chain=3D000000000019d6689c085ae165831e934ff763ae46a2a6c172b=
3f1b60a8ce26f
>=20
> blockchain://ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd391=
8f76c17f?chain=3Dmain
>=20
> (or a different element name maybe)
>=20
> --=20
> Try the Online TrID File Identifier
> http://mark0.net/onlinetrid.aspx
|
