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
|
Return-Path: <btcdrak@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 841C21038
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 22:59:58 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com
[209.85.212.171])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id D45CD10D
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 22:59:57 +0000 (UTC)
Received: by wicmc4 with SMTP id mc4so48264545wic.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 01 Sep 2015 15:59:56 -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=8LrxpXpIq1utMhf1ub54j5NgIgHJKtzgiwmtZC0mUZ0=;
b=V1sTYi2pP+gxKI93wY/dOaMc8DyAOzSR6uFqmpPrckXfcRoe0TRKNFHVuRVFxnY1hj
/t0IHcbhBhu4ZFrVmBKYjJOBqDpnXjWhm+7UZ9+pIRM2xcyhveR+o0QcRzbM6YWyw+ZP
OlUYxXxB14flJa0O2VafR9NVRFVVUQJauRuxSJvn+sBYLJJuJTOUMewfdnOuZccqxYV8
VoEB7df84op6VLcXg0fMR35qb4NGHBEbGqNT0+nEN6bGQ4wxmVVNhPoihMVTuiRSOaco
8RumucntLZRMA/zcl8mZINOxYwrwd/1GmXw3jmpAZ7nydeYnfNoqoiv6cSsVe2jutTwP
evdQ==
X-Received: by 10.180.20.210 with SMTP id p18mr513880wie.6.1441148396555; Tue,
01 Sep 2015 15:59:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.211.16 with HTTP; Tue, 1 Sep 2015 15:59:36 -0700 (PDT)
In-Reply-To: <CAJN5wHVdneuRv6Vpf4q3d=mqwu2HkNeJwFhoqPHFiQcatt4RSg@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>
<CAJN5wHVdneuRv6Vpf4q3d=mqwu2HkNeJwFhoqPHFiQcatt4RSg@mail.gmail.com>
From: Btc Drak <btcdrak@gmail.com>
Date: Tue, 1 Sep 2015 23:59:36 +0100
Message-ID: <CADJgMzuK6YpLyFQ1BnHuWi4GyoqOgnuaA7T3odukpB=Hh3pTgQ@mail.gmail.com>
To: Danny Thorpe <danny.thorpe@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HK_RANDOM_ENVFROM,
HK_RANDOM_FROM, RCVD_IN_DNSWL_LOW autolearn=no 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 22:59:58 -0000
On Tue, Sep 1, 2015 at 5:12 PM, Danny Thorpe via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> 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.
There's nothing stopping two coins having the same magic bytes, but
communicating on separate ports.
> 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.
The only sane way to me see to have cointype like BIP44.
See https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki#coin-type
|
