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
|
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 E850A1304
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 14:34:21 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-la0-f53.google.com (mail-la0-f53.google.com
[209.85.215.53])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id F3B15259
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 14:34:20 +0000 (UTC)
Received: by laeb10 with SMTP id b10so1019467lae.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 01 Sep 2015 07:34:19 -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
:content-type; bh=QpS8yqwHG8Jp5rr8p/G501z6h+XP5JBO9yHomNg+mLs=;
b=zyTXmSh1t1RZFHpnEiKOMX7QXLu80xnrrLueU59WD1I1Jkctbk6MpATkYKdrlkgT2z
3Z049rEGJWUyH1oB0UocpfSjkPAZdJseiZ7SBSx8cSMLRpSBZ6tvktXL+F9RUZ2PWTrT
J3rp3MWPyEc2qo+RwWHteukDwFUGUQOO6ixrvV1VQY/YRvMIqSzIDoXvgMnntWB3jkh3
fQjouGI5ZJROsnWl7JfeZwQSQIL0a87uXTfa5oj5cvAuECGtN1pzblE4KNqVrrO29e9k
lsJs8JGfxE0Xh+xlqJOoZEkkr55gpGkrXrhebQhwNL4fK697QAXj8b+BM4UfIGpKJ1ne
vG1Q==
X-Received: by 10.112.63.138 with SMTP id g10mr13485342lbs.106.1441118059257;
Tue, 01 Sep 2015 07:34:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.114.186.168 with HTTP; Tue, 1 Sep 2015 07:33:59 -0700 (PDT)
In-Reply-To: <mrsscu$9oo$1@ger.gmane.org>
References: <CAE0pACLMcMzHkA=vEx+fiEmq7FA1bXDc4t_hQ+955=r=62V5=g@mail.gmail.com>
<CF21152C-15FA-421C-B369-A9A7DB59865F@ricmoo.com>
<mrsscu$9oo$1@ger.gmane.org>
From: Marco Pontello <marcopon@gmail.com>
Date: Tue, 1 Sep 2015 16:33:59 +0200
Message-ID: <CAE0pACJJ00xgUTujPygj7gEfTrHO2bgi4hZLpSZp9irT_GLnsg@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary=001a1133d38a006551051eb07293
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
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 14:34:22 -0000
--001a1133d38a006551051eb07293
Content-Type: text/plain; charset=UTF-8
That surely make sense.
A URI like that perfectly readable, unambiguous and simple enough.
And nice to see a Wallet developer showing interest for this! :)
On Sat, Aug 29, 2015 at 8:07 PM, Andreas Schildbach via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> On 08/29/2015 06:31 PM, Richard Moore via bitcoin-dev wrote:
>
> > I like the idea of having a standard for this, that all explorers (and
> > even core, eventually) would understand.
> >
> > I would recommend 2 changes though. First, using a real URI scheme,
> > blockchain:// so that we can just use normal URL parsing libraries. The
> > bitcoin: thing leads to additional code to mutate it into a proper URI
> > before passing it to URL parsing. And I think it would be fine to
> > include the type looking up. For example:
> >
> >
> blockchain://blockhash/00000000000000001003e880d500968d51157f210c632e08a652af3576600198
> >
> blockchain://txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a
> > blockchain://block/189000
> > blockchain://address/1RicMooMWxqKczuRCa5D2dnJaUEn9ZJyn
>
> Good thinking! It might make sense to look at the existing de-facto
> standard (e.g. blockexplorer.com, blockchain.info):
>
> /tx/ for transactions
> /block/ for blocks, supports both hash or height
> /address/ for address
>
>
> _______________________________________________
> 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
--001a1133d38a006551051eb07293
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">That surely make sense.<div>A URI like that perfectly read=
able, unambiguous and simple enough.</div><div><br></div><div>And nice to s=
ee a Wallet developer showing interest for this! :)</div></div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On Sat, Aug 29, 2015 at 8:0=
7 PM, Andreas Schildbach via bitcoin-dev <span dir=3D"ltr"><<a href=3D"m=
ailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@=
lists.linuxfoundation.org</a>></span> wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex"><span class=3D"">On 08/29/2015 06:31 PM, Richard Moore via bitcoin-d=
ev wrote:<br>
<br>
> I like the idea of having a standard for this, that all explorers (and=
<br>
> even core, eventually) would understand.<br>
><br>
> I would recommend 2 changes though. First, using a real URI scheme,<br=
>
> blockchain:// so that we can just use normal URL parsing libraries. Th=
e<br>
> bitcoin: thing leads to additional code to mutate it into a proper URI=
<br>
> before passing it to URL parsing. And I think it would be fine to<br>
> include the type looking up. For example:<br>
><br>
> blockchain://blockhash/00000000000000001003e880d500968d51157f210c632e0=
8a652af3576600198<br>
> blockchain://txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc=
3f0f7e04281a<br>
> blockchain://block/189000<br>
> blockchain://address/1RicMooMWxqKczuRCa5D2dnJaUEn9ZJyn<br>
<br>
</span>Good thinking! It might make sense to look at the existing de-facto<=
br>
standard (e.g. <a href=3D"http://blockexplorer.com" rel=3D"noreferrer" targ=
et=3D"_blank">blockexplorer.com</a>, <a href=3D"http://blockchain.info" rel=
=3D"noreferrer" target=3D"_blank">blockchain.info</a>):<br>
<br>
/tx/ for transactions<br>
/block/ for blocks, supports both hash or height<br>
/address/ for address<br>
<div class=3D"HOEnZb"><div class=3D"h5"><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.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</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>
--001a1133d38a006551051eb07293--
|
