MIME-Version: 1.0
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
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] RFC - BIP: URI scheme for Blockchain exploration
Precedence: list

--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--