summaryrefslogtreecommitdiff
path: root/ea/3d9daf75df9de8adef27af40d027508e00669b
blob: fd14da1f53549fb0009a2528ac1c5ed722a41bc1 (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
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
Return-Path: <danny.thorpe@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 7CCAE13ED
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue,  1 Sep 2015 16:12:44 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-oi0-f51.google.com (mail-oi0-f51.google.com
	[209.85.218.51])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 1544524E
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue,  1 Sep 2015 16:12:43 +0000 (UTC)
Received: by oibi136 with SMTP id i136so2400477oib.3
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 01 Sep 2015 09:12:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=0LmkJTIsflZLHQwbwkWn8P0lhwVQ8gUGst5XKXP2Qlc=;
	b=RjQn7++ePO5dZgkRr/hJgDrbrgVCULne0k3QGfTekVVRS/MbHpfT3gyTFKChYTC+HF
	NakkEleZGIBCOvi3uZWg2bBWuX9iQ9TDGenbchjP7VrEsQGMtcFhz9/GiiOY+POzINcH
	LZ3yshs/Q8314pV0IL0vquJwJTN8cSpbZzqL39aBx5w1Xn+tczzMluLwMZ5mJ+YYkX8I
	0D/XN6rSPooOV9a4goed1iy8r9JUqbZ6wXN9O6ZZttOwuZ35gCvtvsebLR2ZRoY5aKiS
	xy0uhOs1hgsOv09j9NjfJNGz3I+fD79OfhkPuENoJSv6mdChtDh7ZZel2IV1uWKyxGoI
	n8tw==
MIME-Version: 1.0
X-Received: by 10.202.243.136 with SMTP id r130mr17060713oih.39.1441123962432; 
	Tue, 01 Sep 2015 09:12:42 -0700 (PDT)
Received: by 10.202.204.22 with HTTP; Tue, 1 Sep 2015 09:12:42 -0700 (PDT)
In-Reply-To: <CABm2gDpC55dsr4GNAUabgnOeXcNTrgHSAtM7Jqfp0_QUfjXmoQ@mail.gmail.com>
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>
	<CABm2gDpC55dsr4GNAUabgnOeXcNTrgHSAtM7Jqfp0_QUfjXmoQ@mail.gmail.com>
Date: Tue, 1 Sep 2015 09:12:42 -0700
Message-ID: <CAJN5wHVdneuRv6Vpf4q3d=mqwu2HkNeJwFhoqPHFiQcatt4RSg@mail.gmail.com>
From: Danny Thorpe <danny.thorpe@gmail.com>
To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
Content-Type: multipart/alternative; boundary=94eb2c0944e0dbb833051eb1d1c6
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 16:12:44 -0000

--94eb2c0944e0dbb833051eb1d1c6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Rather than using an inhumanly long hex string from the genesis hash to
distinguish between mainnet and testnet, why not use the network magic
bytes instead? Much shorter, just as distinct.

I'd still prefer a common network name mapping for the sake of humanity.
Few bitcoin library implementations use the same string names for mainnet
and testnet. This BIP could simply define one string name alias for each
supported network and leave mapping to local lingo to the implementors.

-Danny

On Sat, Aug 29, 2015 at 1:10 PM, Jorge Tim=C3=B3n <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> 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 name=
s.
> >
> > You'd have to do something like:
> >
> >
> blockchain:?network=3Dtestnet&txid=3D3b95a766d7a99b87188d6875c8484cb2b310=
b78459b7816d4dfc3f0f7e04281a
>
> 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 agree with Andreas Schildbach that respecting the most commonly used
> schemes is desirable.
> So my preference would be:
>
>
> /tx/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a?chai=
n=3D000000000933ea01ad0ee984209779baaec3ced90fa3f408719526f8d77f4943
>
> (a tx in testnet)
>
>
> /block/00000000000000000b0d504d142ac8bdd1a2721d19f423a8146d0d6de882167b?c=
hain=3D000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f
>
> (a block in bitcoin's mainnet)
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

--94eb2c0944e0dbb833051eb1d1c6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Rather than using an inhumanly long hex string from the ge=
nesis hash to distinguish between mainnet and testnet, why not use the netw=
ork magic bytes instead? Much shorter, just as distinct.<div><br></div><div=
>I&#39;d still prefer a common network name mapping for the sake of humanit=
y. Few bitcoin library implementations use the same string names for mainne=
t and testnet. This BIP could simply define one string name alias for each =
supported network and leave mapping to local lingo to the implementors.</di=
v><div><br></div><div>-Danny</div></div><div class=3D"gmail_extra"><br><div=
 class=3D"gmail_quote">On Sat, Aug 29, 2015 at 1:10 PM, Jorge Tim=C3=B3n <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org=
" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>&gt;</span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex"><span class=3D"">On Sat, Aug 29, 201=
5 at 9:01 PM, Matt Whitlock via bitcoin-dev<br>
&lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@li=
sts.linuxfoundation.org</a>&gt; wrote:<br>
&gt; That&#39;s still not right, since &quot;mainnet&quot; and &quot;testne=
t&quot; are not host names.<br>
&gt;<br>
&gt; You&#39;d have to do something like:<br>
&gt;<br>
&gt; blockchain:?network=3Dtestnet&amp;txid=3D3b95a766d7a99b87188d6875c8484=
cb2b310b78459b7816d4dfc3f0f7e04281a<br>
<br>
</span>I would really prefer chain=3D&lt;chainID&gt; over network=3D&lt;cha=
inPetnameStr&gt;<br>
By chainID I mean the hash of the genesis block, see<br>
<a href=3D"https://github.com/jtimon/bitcoin/commit/3191d5e8e75687a27cf466b=
7a4c70bdc04809d39" rel=3D"noreferrer" target=3D"_blank">https://github.com/=
jtimon/bitcoin/commit/3191d5e8e75687a27cf466b7a4c70bdc04809d39</a><br>
I&#39;m completely fine with doing that using an optional parameter (for<br=
>
backwards compatibility).<br>
<br>
I agree with Andreas Schildbach that respecting the most commonly used<br>
schemes is desirable.<br>
So my preference would be:<br>
<br>
/tx/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a?chain=
=3D000000000933ea01ad0ee984209779baaec3ced90fa3f408719526f8d77f4943<br>
<br>
(a tx in testnet)<br>
<br>
/block/00000000000000000b0d504d142ac8bdd1a2721d19f423a8146d0d6de882167b?cha=
in=3D000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f<br>
<br>
(a block in bitcoin&#39;s mainnet)<br>
<div class=3D"HOEnZb"><div class=3D"h5">___________________________________=
____________<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></div>

--94eb2c0944e0dbb833051eb1d1c6--