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
|
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 <gronager@ceptacle.com>) id 1RzVTH-0000mw-AF
for bitcoin-development@lists.sourceforge.net;
Mon, 20 Feb 2012 15:48:11 +0000
X-ACL-Warn:
Received: from 2508ds5-oebr.0.fullrate.dk ([95.166.54.49]
helo=mail.ceptacle.com)
by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1RzVTB-0001ls-C9 for bitcoin-development@lists.sourceforge.net;
Mon, 20 Feb 2012 15:48:11 +0000
Received: from localhost (localhost [127.0.0.1])
by mail.ceptacle.com (Postfix) with ESMTP id 665D917AA32C;
Mon, 20 Feb 2012 16:47:59 +0100 (CET)
X-Virus-Scanned: amavisd-new at ceptacle.com
Received: from mail.ceptacle.com ([127.0.0.1])
by localhost (server.ceptacle.private [127.0.0.1]) (amavisd-new,
port 10024)
with ESMTP id gBc3yMagg1pN; Mon, 20 Feb 2012 16:47:54 +0100 (CET)
Received: from [10.0.1.28] (2508ds5-oebr.0.fullrate.dk [95.166.54.49])
by mail.ceptacle.com (Postfix) with ESMTPSA id 2DC1417AA31E;
Mon, 20 Feb 2012 16:47:54 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?Michael_Gr=F8nager?= <gronager@ceptacle.com>
In-Reply-To: <201202200918.38484.luke@dashjr.org>
Date: Mon, 20 Feb 2012 16:47:53 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <9BF2FBEB-5F85-45A8-8343-0F160A28483B@ceptacle.com>
References: <3DA9C79B-D91D-48B2-9469-37BAA037FC50@ceptacle.com>
<201202200918.38484.luke@dashjr.org>
To: "Luke-Jr" <luke@dashjr.org>
X-Mailer: Apple Mail (2.1257)
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1RzVTB-0001ls-C9
Cc: bitcoin-development@lists.sourceforge.net
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 15:48:11 -0000
>=20
>> 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.
>=20
> Where do you see this? It has always been "version" as far as I am =
aware, and=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.
See: =
https://en.bitcoin.it/wiki/Technical_background_of_Bitcoin_addresses
And the attached graphics - here it is defined as network byte and =
network id.
Anyway - can probably live with some bit level subdivision into network =
id and address class.
/M=
|
