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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <wtogami@gmail.com>) id 1Wk9Gx-00043r-1s
for bitcoin-development@lists.sourceforge.net;
Tue, 13 May 2014 09:45:19 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.47 as permitted sender)
client-ip=209.85.213.47; envelope-from=wtogami@gmail.com;
helo=mail-yh0-f47.google.com;
Received: from mail-yh0-f47.google.com ([209.85.213.47])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Wk9Gv-0003W7-Ub
for bitcoin-development@lists.sourceforge.net;
Tue, 13 May 2014 09:45:19 +0000
Received: by mail-yh0-f47.google.com with SMTP id z6so58740yhz.20
for <bitcoin-development@lists.sourceforge.net>;
Tue, 13 May 2014 02:45:12 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.236.123.49 with SMTP id u37mr6456651yhh.34.1399974312483;
Tue, 13 May 2014 02:45:12 -0700 (PDT)
Received: by 10.170.58.77 with HTTP; Tue, 13 May 2014 02:45:12 -0700 (PDT)
Date: Mon, 12 May 2014 23:45:12 -1000
Message-ID: <CAEz79Prrpwi6SXyCpGesmkdau6vjtwELAhr6quXtFZ6_t1-y2A@mail.gmail.com>
From: "Warren Togami Jr." <wtogami@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=20cf301b68559720c804f944eb59
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(wtogami[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1Wk9Gv-0003W7-Ub
Subject: [Bitcoin-development] Regtest Address Version Change Proposal
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: Tue, 13 May 2014 09:45:19 -0000
--20cf301b68559720c804f944eb59
Content-Type: text/plain; charset=UTF-8
Hi folks,
I propose changing all of the address versions in -regtest mode to be
unique so they are no longer identical to testnet.
https://en.bitcoin.it/wiki/List_of_address_prefixes
For example, regtest pubkey hash addresses could begin with r or R.
We need to know if any existing tools would need to be modified to support
this change to regtest. Do existing tools outside of pull tester expect
regtest to have testnet addresses? If the quantity of tools that currently
handle regtest is small then we can modify them to the new address versions.
Warren Togami
--20cf301b68559720c804f944eb59
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hi folks,<div><br></div><div>I propose changing all of the=
address versions in -regtest mode to be unique so they are no longer ident=
ical to testnet.</div><div><br></div><div><a href=3D"https://en.bitcoin.it/=
wiki/List_of_address_prefixes">https://en.bitcoin.it/wiki/List_of_address_p=
refixes</a><br>
</div><div>For example, regtest pubkey hash addresses could begin with r or=
R.</div><div><br></div><div>We need to know if any existing tools would ne=
ed to be modified to support this change to regtest. =C2=A0Do existing tool=
s outside of pull tester expect regtest to have testnet addresses? =C2=A0If=
the quantity of tools that currently handle regtest is small then we can m=
odify them to the new address versions.</div>
<div><br></div><div>Warren Togami</div><div><br></div></div>
--20cf301b68559720c804f944eb59--
|
