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
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
|
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 E3ECA71
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 18 Nov 2015 12:32:09 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-lb0-f180.google.com (mail-lb0-f180.google.com
[209.85.217.180])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 195AB8C
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 18 Nov 2015 12:32:08 +0000 (UTC)
Received: by lbbkw15 with SMTP id kw15so23497526lbb.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 18 Nov 2015 04:32:06 -0800 (PST)
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=OcpuhOIYYgzYWX8uNxlUs/i/jAWPChuvkwnt23M/Xxs=;
b=UUmHY3iXH+z9LXbQCV5Ph8TU/MwdA1IPQu/m9VhT2pVSst6Z0HWuTnmvpI27zLKl8W
B/wKBDVSbyU/lMvz1nWEB8CI568dbVIAN/XborjKlWLbTGi+X0z7IN1DA5rWPoXfXDz1
Q24cX8G2j61YmM6OKwAaUuHg4S2t4TUW954+txh47bB6aup+HDigzibIsJSuI642/K7w
W8nLV/FKH8MaTJkAx5kxxejEs1qNy1JfdcyOmcZ8s/tyhG92tiOsN+N9xXcU1PM6O+pQ
ZBPyfTbirvim2l/UfxC5swUOYqavosGk6Fz2Hg8Oy3dr1u3JJIWJvCH83zOABNkSatpb
zpIQ==
X-Received: by 10.112.14.234 with SMTP id s10mr575799lbc.136.1447849926140;
Wed, 18 Nov 2015 04:32:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.114.186.106 with HTTP; Wed, 18 Nov 2015 04:31:46 -0800 (PST)
In-Reply-To: <CABm2gDoOMD0zujY+GGRrQ7HcZ9uBpk_diW+rB0wLzj61=qmt7w@mail.gmail.com>
References: <CAE0pACLMcMzHkA=vEx+fiEmq7FA1bXDc4t_hQ+955=r=62V5=g@mail.gmail.com>
<CAE0pACLzGPHs7-KG+fzbYJzbDZ+qxkoko_uPz4Kc-1ov8jdMsA@mail.gmail.com>
<CABm2gDrutCDFAVbXAFUaAZfoHK_sKzX6ZsMpD0j=f7HJj99Zpg@mail.gmail.com>
<CAE0pACLyuaU=gJji1DkC1xkpmRjCFdRReLHa8zsD04+aDDQLeA@mail.gmail.com>
<CABm2gDrz7iEoA6bMsFc-U4VNCKepSZ44tiT3_WfUPS=MR2eOmw@mail.gmail.com>
<CAE0pACK1Jp-GGZ84m-m8qNZXnOXvJfRXd+1SJk48wFYp02RX_Q@mail.gmail.com>
<CABm2gDoOMD0zujY+GGRrQ7HcZ9uBpk_diW+rB0wLzj61=qmt7w@mail.gmail.com>
From: Marco Pontello <marcopon@gmail.com>
Date: Wed, 18 Nov 2015 13:31:46 +0100
Message-ID: <CAE0pACKqrO0X+XBjkEASz+T8YK_VdRdxhWYo0mUkOkJjjuzctA@mail.gmail.com>
To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
Content-Type: multipart/alternative; boundary=001a1132fc5c892c380524cfd450
X-Spam-Status: No, score=-1.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_LOW, URIBL_BLACK autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Wed, 18 Nov 2015 12:34:00 +0000
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: Wed, 18 Nov 2015 12:32:10 -0000
--001a1132fc5c892c380524cfd450
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Right, now it should be ok. Thanks.
On Wed, Nov 18, 2015 at 12:29 PM, Jorge Tim=C3=B3n <jtimon@jtimon.cc> wrote=
:
> I can always link to the BIP when I reopen that commit as independent
> instead of the other way around.
> Btw, the PR needs rebase (probably the conflict is in the README).
>
> On Mon, Nov 16, 2015 at 11:10 PM, Marco Pontello <marcopon@gmail.com>
> wrote:
> > OK, adding the relevant code fragment is probably the simplest and dire=
ct
> > option. Done.
> >
> > On Mon, Nov 16, 2015 at 3:43 PM, Jorge Tim=C3=B3n <jtimon@jtimon.cc> wr=
ote:
> >>
> >> Not a native english speaker myself, so I may have missed some things.=
..
> >>
> >> Yes, sorry about the link. I guess you can point to #6230 . I can
> >> rebase it if needed but I would close it again because I don't want to
> >> have too many things from #6382 opened at the same time (is noisy and
> >> worse for review). My plan was to not open it independently at least
> >> until after #6907 (and actually after 0.12 assuming #6907 gets in by
> >> 0.12). But then I would maybe open a new one and reference the old one
> >> rather than reopening #6230 (which tends to be confusing).
> >> I'm not really sure what's the best answer here...but #6382 is
> >> certainly going to need rebase and the link will be broken again.
> >> Maybe one answer is to copy some text from #6230 or the commit and add
> >> it directly to the BIP instead of referencing to that commit (which
> >> will be, at least until #6907 is merged, a moving target).
> >>
> >> On Mon, Nov 16, 2015 at 1:59 AM, Marco Pontello <marcopon@gmail.com>
> >> wrote:
> >> > Thanks for the comments! Now I fixed the typos (hope to have got the=
m
> >> > all,
> >> > English isn't my first language), clarified the chain part a bit, an=
d
> >> > fixed
> >> > the link. There probably is a better way to reference that source co=
de
> >> > part
> >> > with the genesis blocks hashs, in a way that doesn't need to be
> changed,
> >> > maybe...
> >> >
> >> > Now the main change would be to put in a proper BIP number! :)
> >> >
> >> > On Sun, Nov 15, 2015 at 12:42 PM, Jorge Tim=C3=B3n <jtimon@jtimon.cc=
>
> wrote:
> >> >>
> >> >> Thank you for incorporating the feedback, specifically thank you fo=
r
> >> >> 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
> >> >> <bitcoin-dev@lists.linuxfoundation.org> 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 t=
he
> >> >> > 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 mor=
e
> >> >> > 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 blo=
ck
> >> >> > 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 <
> marcopon@gmail.com>
> >> >> > 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
> >> >> >> =3D=3D=3D=3D=3D=3D=3D=3D
> >> >> >> This BIP propose a simple URI scheme for looking up blocks,
> >> >> >> transactions,
> >> >> >> addresses on a Blockchain explorer.
> >> >> >>
> >> >> >> Motivation
> >> >> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >> >> >> 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
> >> >> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >> >> >> The URI follow this simple form:
> >> >> >>
> >> >> >> blockchain: <hash/string>
> >> >> >>
> >> >> >> Examples:
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> blockchain:00000000000000001003e880d500968d51157f210c632e08a652af35766001=
98
> >> >> >> blockchain:001949
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> blockchain:3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e0428=
1a
> >> >> >>
> >> >> >> Rationale
> >> >> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D
> >> >> >> 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, witho=
ut
> >> >> >> having
> >> >> >> to worry about any specific Blockchain explorer or provide a mea=
ns
> >> >> >> 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
> >> >> >
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > 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
--001a1132fc5c892c380524cfd450
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Right, now it should be ok. Thanks.</div><div class=3D"gma=
il_extra"><br><div class=3D"gmail_quote">On Wed, Nov 18, 2015 at 12:29 PM, =
Jorge Tim=C3=B3n <span dir=3D"ltr"><<a href=3D"mailto:jtimon@jtimon.cc" =
target=3D"_blank">jtimon@jtimon.cc</a>></span> wrote:<br><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">I can always link to the BIP when I reopen that commit as i=
ndependent<br>
instead of the other way around.<br>
Btw, the PR needs rebase (probably the conflict is in the README).<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On Mon, Nov 16, 2015 at 11:10 PM, Marco Pontello <<a href=3D"mailto:marc=
opon@gmail.com">marcopon@gmail.com</a>> wrote:<br>
> OK, adding the relevant code fragment is probably the simplest and dir=
ect<br>
> option. Done.<br>
><br>
> On Mon, Nov 16, 2015 at 3:43 PM, Jorge Tim=C3=B3n <jtimon@jtimon.cc=
> wrote:<br>
>><br>
>> Not a native english speaker myself, so I may have missed some thi=
ngs...<br>
>><br>
>> Yes, sorry about the link. I guess you can point to #6230 . I can<=
br>
>> rebase it if needed but I would close it again because I don't=
want to<br>
>> have too many things from #6382 opened at the same time (is noisy =
and<br>
>> worse for review). My plan was to not open it independently at lea=
st<br>
>> until after #6907 (and actually after 0.12 assuming #6907 gets in =
by<br>
>> 0.12). But then I would maybe open a new one and reference the old=
one<br>
>> rather than reopening #6230 (which tends to be confusing).<br>
>> I'm not really sure what's the best answer here...but #638=
2 is<br>
>> certainly going to need rebase and the link will be broken again.<=
br>
>> Maybe one answer is to copy some text from #6230 or the commit and=
add<br>
>> it directly to the BIP instead of referencing to that commit (whic=
h<br>
>> will be, at least until #6907 is merged, a moving target).<br>
>><br>
>> On Mon, Nov 16, 2015 at 1:59 AM, Marco Pontello <<a href=3D"mai=
lto:marcopon@gmail.com">marcopon@gmail.com</a>><br>
>> wrote:<br>
>> > Thanks for the comments! Now I fixed the typos (hope to have =
got them<br>
>> > all,<br>
>> > English isn't my first language), clarified the chain par=
t a bit, and<br>
>> > fixed<br>
>> > the link. There probably is a better way to reference that so=
urce code<br>
>> > part<br>
>> > with the genesis blocks hashs, in a way that doesn't need=
to be changed,<br>
>> > maybe...<br>
>> ><br>
>> > Now the main change would be to put in a proper BIP number! :=
)<br>
>> ><br>
>> > On Sun, Nov 15, 2015 at 12:42 PM, Jorge Tim=C3=B3n <jtimon=
@jtimon.cc> wrote:<br>
>> >><br>
>> >> Thank you for incorporating the feedback, specifically th=
ank you for<br>
>> >> using the genesis block hash as the unique chain ID.<br>
>> >><br>
>> >> I wen't through the BIP draft and left a few of comme=
nts, but I really<br>
>> >> like its simplicity and focus. Good work!<br>
>> >><br>
>> >> On Sun, Nov 15, 2015 at 3:14 AM, Marco Pontello via bitco=
in-dev<br>
>> >> <<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.o=
rg">bitcoin-dev@lists.linuxfoundation.org</a>> wrote:<br>
>> >> > Hi!<br>
>> >> ><br>
>> >> > To anyone that followed the discussion (from some ti=
me ago) about the<br>
>> >> > proposed new URI for Blockchain references / explora=
tion, I just<br>
>> >> > wanted<br>
>> >> > to<br>
>> >> > point out that I have collected the feedback provide=
d, reworked the<br>
>> >> > text,<br>
>> >> > put the BIP on GitHub and created a pull request:<br=
>
>> >> ><br>
>> >> ><br>
>> >> > <a href=3D"https://github.com/MarcoPon/bips/blob/mas=
ter/bip-MarcoPon-01.mediawiki" rel=3D"noreferrer" target=3D"_blank">https:/=
/github.com/MarcoPon/bips/blob/master/bip-MarcoPon-01.mediawiki</a><br>
>> >> > <a href=3D"https://github.com/bitcoin/bips/pull/202"=
rel=3D"noreferrer" target=3D"_blank">https://github.com/bitcoin/bips/pull/=
202</a><br>
>> >> ><br>
>> >> > The need for an URI for this come to mind again in t=
he last days<br>
>> >> > looking<br>
>> >> > at<br>
>> >> > Eternity Wall, which IMHO provide a use case that we=
will see more<br>
>> >> > and<br>
>> >> > more<br>
>> >> > in the (near) future: <a href=3D"http://eternitywall=
.it/" rel=3D"noreferrer" target=3D"_blank">http://eternitywall.it/</a><br>
>> >> > Using that service, when you want to check for the p=
roof that a<br>
>> >> > specific<br>
>> >> > message was written in the Blockchain, it let you ch=
oose from 5<br>
>> >> > different<br>
>> >> > explorer.<br>
>> >> > Mycelium wallet recently added the option to select =
one of 15 block<br>
>> >> > explorers.<br>
>> >> > And there's the crypto_bot on reddit/r/bitcoin t=
hat detect reference<br>
>> >> > to<br>
>> >> > transaction an add a message with links to 7 differe=
nt explorers.<br>
>> >> ><br>
>> >> > I think that's clearly something that's need=
ed.<br>
>> >> ><br>
>> >> > Bye!<br>
>> >> ><br>
>> >> ><br>
>> >> > On Sat, Aug 29, 2015 at 1:48 PM, Marco Pontello <=
<a href=3D"mailto:marcopon@gmail.com">marcopon@gmail.com</a>><br>
>> >> > wrote:<br>
>> >> >><br>
>> >> >> Hi!<br>
>> >> >> My first post here, hope I'm following the r=
ight conventions.<br>
>> >> >> I had this humble idea for a while, so I thought=
to go ahead and<br>
>> >> >> propose<br>
>> >> >> it.<br>
>> >> >><br>
>> >> >> BIP: XX<br>
>> >> >> Title: URI scheme for Blockchain exploration<br>
>> >> >> Author: Marco Pontello<br>
>> >> >> Status: Draft<br>
>> >> >> Type: Standards Track<br>
>> >> >> Created: 29 August 2015<br>
>> >> >><br>
>> >> >> Abstract<br>
>> >> >> =3D=3D=3D=3D=3D=3D=3D=3D<br>
>> >> >> This BIP propose a simple URI scheme for looking=
up blocks,<br>
>> >> >> transactions,<br>
>> >> >> addresses on a Blockchain explorer.<br>
>> >> >><br>
>> >> >> Motivation<br>
>> >> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
>> >> >> The purpose of this URI scheme is to enable user=
s to handle all the<br>
>> >> >> requests for details about blocks, transactions,=
etc. with their<br>
>> >> >> preferred<br>
>> >> >> tool (being that a web service or a local applic=
ation).<br>
>> >> >><br>
>> >> >> Currently a Bitcoin client usually point to an a=
rbitrary blockchain<br>
>> >> >> explorer when the user look for the details of a=
transaction (es.<br>
>> >> >> Bitcoin<br>
>> >> >> Wallet use BitEasy, Mycelium or Electrum use Blo=
ckchain.info, etc.).<br>
>> >> >> Other times resorting to cut&paste is needed=
.<br>
>> >> >> The same happens with posts and messages that re=
ference some<br>
>> >> >> particular<br>
>> >> >> txs or blocks, if they provide links at all.<br>
>> >> >><br>
>> >> >> Specification<br>
>> >> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
>> >> >> The URI follow this simple form:<br>
>> >> >><br>
>> >> >> blockchain: <hash/string><br>
>> >> >><br>
>> >> >> Examples:<br>
>> >> >><br>
>> >> >><br>
>> >> >><br>
>> >> >><br>
>> >> >> blockchain:00000000000000001003e880d500968d51157=
f210c632e08a652af3576600198<br>
>> >> >> blockchain:001949<br>
>> >> >><br>
>> >> >><br>
>> >> >><br>
>> >> >> blockchain:3b95a766d7a99b87188d6875c8484cb2b310b=
78459b7816d4dfc3f0f7e04281a<br>
>> >> >><br>
>> >> >> Rationale<br>
>> >> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
>> >> >> I thought about using some more complex scheme, =
or adding qualifiers<br>
>> >> >> to<br>
>> >> >> distinguish blocks from txs, but in the end I th=
ink that keeping it<br>
>> >> >> simple<br>
>> >> >> should be practical enough. Blockchain explorers=
can apply the same<br>
>> >> >> disambiguation rules they are already using to p=
rocess the usual<br>
>> >> >> search<br>
>> >> >> box.<br>
>> >> >><br>
>> >> >> From the point of view of a wallet developer (or=
other tool that<br>
>> >> >> need<br>
>> >> >> to<br>
>> >> >> show any kind of Blockchain references), using t=
his scheme mean that<br>
>> >> >> he<br>
>> >> >> can simply make it a blockchain: link and be don=
e with it, without<br>
>> >> >> having<br>
>> >> >> to worry about any specific Blockchain explorer =
or provide a means<br>
>> >> >> for<br>
>> >> >> the<br>
>> >> >> user to select one.<br>
>> >> >><br>
>> >> >> Blockchain explorers in turn will simply offer t=
o handle the<br>
>> >> >> blockchain:<br>
>> >> >> URI, the first time the user visit their website=
, or launch/install<br>
>> >> >> the<br>
>> >> >> application, or even set themselves if there isn=
't already one.<br>
>> >> >><br>
>> >> >> Users get the convenience of using always their =
preferred explorer,<br>
>> >> >> which<br>
>> >> >> can be especially handy on mobile devices, where=
juggling with<br>
>> >> >> cut&paste<br>
>> >> >> is far from ideal.<br>
>> >> >><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>
>> >> ><br>
>> >> > _______________________________________________<br>
>> >> > bitcoin-dev mailing list<br>
>> >> > <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.=
org">bitcoin-dev@lists.linuxfoundation.org</a><br>
>> >> > <a href=3D"https://lists.linuxfoundation.org/mailman=
/listinfo/bitcoin-dev" rel=3D"noreferrer" target=3D"_blank">https://lists.l=
inuxfoundation.org/mailman/listinfo/bitcoin-dev</a><br>
>> >> ><br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> > --<br>
>> > Try the Online TrID File Identifier<br>
>> > <a href=3D"http://mark0.net/onlinetrid.aspx" rel=3D"noreferre=
r" 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>
--001a1132fc5c892c380524cfd450--
|
