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
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
|
Return-Path: <marcopon@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 0A54910B4
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 21:44:02 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-lb0-f174.google.com (mail-lb0-f174.google.com
[209.85.217.174])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 06CD61B0
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 21:43:59 +0000 (UTC)
Received: by lbpo4 with SMTP id o4so7547184lbp.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 01 Sep 2015 14:43:58 -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
:cc:content-type;
bh=oGtmUb8ZMmCWkDLpZnOpcum3R/0FuObRPSnt/Kbv4Jw=;
b=AlcrIvN+cyRGrYzSfcsbAP9nRzCO3dnVcR7/NvPXyFrgUslQNqxMyI9OHRvqaHOMMh
A8D/btZogHlakcrLXlp2IxJ5vQloQ3tXKMGeu7426TM6GeYei9EqwcecdRoKJ3yrFHjl
PER0i2LW/33CqkTEl4MOrRFBOA5COMstu+MNzzBJ7KrF05/ItzSOF7Ke3ePi588fRoOy
aZe4JOmi6qjUG8neg2NNKrWucetjreDRmbEmzTlJ/hHtuldQRMAA27RZsRE9QG6aLKfl
SmltjFmHiIi6sNpjUpRuMVVmKrNGkXM9/0E+19EksjYDzXBNIsVTQ5dpOua7tlGANKXq
aWXw==
X-Received: by 10.112.129.72 with SMTP id nu8mr9731017lbb.81.1441143838571;
Tue, 01 Sep 2015 14:43:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.114.186.168 with HTTP; Tue, 1 Sep 2015 14:43:39 -0700 (PDT)
In-Reply-To: <1842396.ZYjkpCDfSt@crushinator>
References: <CAE0pACLMcMzHkA=vEx+fiEmq7FA1bXDc4t_hQ+955=r=62V5=g@mail.gmail.com>
<5546682.RnG4VcateO@crushinator>
<CAE0pACLQZC9Tuggwerah4LruVTfFpbOnvo0oKj4EYU8yJ9VXuQ@mail.gmail.com>
<1842396.ZYjkpCDfSt@crushinator>
From: Marco Pontello <marcopon@gmail.com>
Date: Tue, 1 Sep 2015 23:43:39 +0200
Message-ID: <CAE0pACJqdCVLbz5UNCSqO11YCMV97ejoBAC6PRXFz=mFJQH6rA@mail.gmail.com>
To: Matt Whitlock <bip@mattwhitlock.name>
Content-Type: multipart/alternative; boundary=047d7b3a8c60918618051eb67230
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
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:44:02 -0000
--047d7b3a8c60918618051eb67230
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Oh, my bad! Right, sounds pretty good to me then.
On Tue, Sep 1, 2015 at 11:42 PM, Matt Whitlock <bip@mattwhitlock.name>
wrote:
> The authority part in a URI is optional.
>
>
> blockchain:/tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f=
76c17f
>
> Notice the lack of a double-slash.
>
>
> On Tuesday, 1 September 2015, at 11:38 pm, Marco Pontello wrote:
> > I see your point. But I personally like that the chain part could be
> > optional, given that the vast majority of the references in the end wil=
l
> be
> > to Bitcoin main net.
> >
> > On Tue, Sep 1, 2015 at 11:16 PM, Matt Whitlock <bip@mattwhitlock.name>
> > wrote:
> >
> > > Isn't this all backward? The "authority" component of the URL should
> > > identify the chain, and the "path" component should identify the
> particular
> > > block, tx, or address in that chain.
> > >
> > > So instead of:
> > >
> > >
> > >
> blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918=
f76c17f?chain=3D000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8=
ce26f
> > >
> > > It should be:
> > >
> > >
> > >
> blockchain://000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8c=
e26f/tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f76c17f
> > >
> > > And I would agree with allowing well-known chains to register a name,
> to
> > > be used as an alternative to the literal, hash syntax:
> > >
> > >
> > >
> blockchain://bitcoin/tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f2=
4ecd3918f76c17f
> > >
> > >
> > > On Tuesday, 1 September 2015, at 4:49 pm, Marco Pontello wrote:
> > > > On Sat, Aug 29, 2015 at 10:10 PM, Jorge Tim=C3=B3n <
> > > > bitcoin-dev@lists.linuxfoundation.org> wrote:
> > > >
> > > > >
> > > > > I would really prefer chain=3D<chainID> over
> network=3D<chainPetnameStr>
> > > > > By chainID I mean the hash of the genesis block, see
> > > > >
> > > > >
> > >
> https://github.com/jtimon/bitcoin/commit/3191d5e8e75687a27cf466b7a4c70bdc=
04809d39
> > > > > 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/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918=
f76c17f
> > > >
> > > >
> > >
> blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918=
f76c17f?chain=3D000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8=
ce26f
> > > >
> > > >
> > >
> blockchain://ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f76=
c17f?chain=3Dmain
> > > >
> > > > (or a different element name maybe)
> > > >
> > > > --
> > > > Try the Online TrID File Identifier
> > > > http://mark0.net/onlinetrid.aspx
> > >
> >
> >
> >
> > --
> > Try the Online TrID File Identifier
> > http://mark0.net/onlinetrid.aspx
>
--=20
Try the Online TrID File Identifier
http://mark0.net/onlinetrid.aspx
--047d7b3a8c60918618051eb67230
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Oh, my bad! Right, sounds pretty good to me then.</div><di=
v class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Sep 1, 2015 =
at 11:42 PM, Matt Whitlock <span dir=3D"ltr"><<a href=3D"mailto:bip@matt=
whitlock.name" target=3D"_blank">bip@mattwhitlock.name</a>></span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">The authority part in a URI is optional=
.<br>
<br>
blockchain:/tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f76=
c17f<br>
<br>
Notice the lack of a double-slash.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
On Tuesday, 1 September 2015, at 11:38 pm, Marco Pontello wrote:<br>
> I see your point. But I personally like that the chain part could be<b=
r>
> optional, given that the vast majority of the references in the end wi=
ll be<br>
> to Bitcoin main net.<br>
><br>
> On Tue, Sep 1, 2015 at 11:16 PM, Matt Whitlock <<a href=3D"mailto:b=
ip@mattwhitlock.name">bip@mattwhitlock.name</a>><br>
> wrote:<br>
><br>
> > Isn't this all backward? The "authority" component =
of the URL should<br>
> > identify the chain, and the "path" component should ide=
ntify the particular<br>
> > block, tx, or address in that chain.<br>
> ><br>
> > So instead of:<br>
> ><br>
> ><br>
> > blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f2=
4ecd3918f76c17f?chain=3D000000000019d6689c085ae165831e934ff763ae46a2a6c172b=
3f1b60a8ce26f<br>
> ><br>
> > It should be:<br>
> ><br>
> ><br>
> > blockchain://000000000019d6689c085ae165831e934ff763ae46a2a6c172b3=
f1b60a8ce26f/tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f7=
6c17f<br>
> ><br>
> > And I would agree with allowing well-known chains to register a n=
ame, to<br>
> > be used as an alternative to the literal, hash syntax:<br>
> ><br>
> ><br>
> > blockchain://bitcoin/tx/ca26cedeb9cbc94e030891578e0d2b688a2890211=
4f6ad2f24ecd3918f76c17f<br>
> ><br>
> ><br>
> > On Tuesday, 1 September 2015, at 4:49 pm, Marco Pontello wrote:<b=
r>
> > > On Sat, Aug 29, 2015 at 10:10 PM, Jorge Tim=C3=B3n <<br>
> > > <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bit=
coin-dev@lists.linuxfoundation.org</a>> wrote:<br>
> > ><br>
> > > ><br>
> > > > I would really prefer chain=3D<chainID> over netw=
ork=3D<chainPetnameStr><br>
> > > > By chainID I mean the hash of the genesis block, see<br=
>
> > > ><br>
> > > ><br>
> > <a href=3D"https://github.com/jtimon/bitcoin/commit/3191d5e8e7568=
7a27cf466b7a4c70bdc04809d39" rel=3D"noreferrer" target=3D"_blank">https://g=
ithub.com/jtimon/bitcoin/commit/3191d5e8e75687a27cf466b7a4c70bdc04809d39</a=
><br>
> > > > I'm completely fine with doing that using an option=
al parameter (for<br>
> > > > backwards compatibility).<br>
> > > ><br>
> > ><br>
> > > I see that using the genesis block hash would be the perfect=
ly rigorous<br>
> > way<br>
> > > to do it, but what do you think about the possibility of let=
ting also use<br>
> > > the name constants, as a simple / more relaxed alternative? =
That would<br>
> > > spare a source lookup just to write a correct reference to a=
tx, maybe<br>
> > in a<br>
> > > forum or a post.<br>
> > ><br>
> > > So a reference to a certain tx could be either:<br>
> > ><br>
> > ><br>
> > blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f2=
4ecd3918f76c17f<br>
> > ><br>
> > ><br>
> > blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f2=
4ecd3918f76c17f?chain=3D000000000019d6689c085ae165831e934ff763ae46a2a6c172b=
3f1b60a8ce26f<br>
> > ><br>
> > ><br>
> > blockchain://ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ec=
d3918f76c17f?chain=3Dmain<br>
> > ><br>
> > > (or a different element name maybe)<br>
> > ><br>
> > > --<br>
> > > Try the Online TrID File Identifier<br>
> > > <a href=3D"http://mark0.net/onlinetrid.aspx" rel=3D"noreferr=
er" target=3D"_blank">http://mark0.net/onlinetrid.aspx</a><br>
> ><br>
><br>
><br>
><br>
> --<br>
> Try the Online TrID File Identifier<br>
> <a href=3D"http://mark0.net/onlinetrid.aspx" rel=3D"noreferrer" target=
=3D"_blank">http://mark0.net/onlinetrid.aspx</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<div class=3D"gmail_signature">Try the Online TrID File Identifier<br><a hr=
ef=3D"http://mark0.net/onlinetrid.aspx" target=3D"_blank">http://mark0.net/=
onlinetrid.aspx</a></div>
</div>
--047d7b3a8c60918618051eb67230--
|
