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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <luke@dashjr.org>) id 1RzU4u-0004SF-Br
for bitcoin-development@lists.sourceforge.net;
Mon, 20 Feb 2012 14:18:56 +0000
X-ACL-Warn:
Received: from zinan.dashjr.org ([173.242.112.54])
by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1RzU4q-0006vA-CE for bitcoin-development@lists.sourceforge.net;
Mon, 20 Feb 2012 14:18:56 +0000
Received: from ishibashi.localnet (fl-184-4-164-217.dhcp.embarqhsd.net
[184.4.164.217]) (Authenticated sender: luke-jr)
by zinan.dashjr.org (Postfix) with ESMTPSA id A1A77D600A2;
Mon, 20 Feb 2012 14:18:46 +0000 (UTC)
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Date: Mon, 20 Feb 2012 09:18:37 -0500
User-Agent: KMail/1.13.7 (Linux/3.2.2-gentoo; KDE/4.7.4; x86_64; ; )
References: <3DA9C79B-D91D-48B2-9469-37BAA037FC50@ceptacle.com>
In-Reply-To: <3DA9C79B-D91D-48B2-9469-37BAA037FC50@ceptacle.com>
X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583
X-PGP-Key-ID: 665FC11DD53E9583
X-PGP-Keyserver: x-hkp://subkeys.pgp.net
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201202200918.38484.luke@dashjr.org>
X-Spam-Score: -0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
X-Headers-End: 1RzU4q-0006vA-CE
Subject: Re: [Bitcoin-development] BIP-13
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2012 14:18:56 -0000
On Monday, February 20, 2012 6:17:01 AM Michael Gr=F8nager wrote:
> Just posted this on the wiki BIP-13 discussion - should I make it into a
> BIP of its own ?
If you must. However, BIP 13 has been pretty much undisputed, and only held=
=20
back by BIP 16/17 so far...
> The "version" portion of the address has so far been labeled "network id",
> and indicates from which network and which chain the address can be used
> for.
Where do you see this? It has always been "version" as far as I am aware, a=
nd=20
we discussed formalizing the details of the bits in it a few months back.
In any case, it was certainly originally intended as "version" as can be=20
observed in Satoshi's reference implementation.
|
