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
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1Y5VB6-0007TY-4J
for bitcoin-development@lists.sourceforge.net;
Mon, 29 Dec 2014 07:55:48 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.49 as permitted sender)
client-ip=74.125.82.49; envelope-from=mh.in.england@gmail.com;
helo=mail-wg0-f49.google.com;
Received: from mail-wg0-f49.google.com ([74.125.82.49])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Y5VAq-0008SU-RJ
for bitcoin-development@lists.sourceforge.net;
Mon, 29 Dec 2014 07:55:48 +0000
Received: by mail-wg0-f49.google.com with SMTP id n12so18169026wgh.8
for <bitcoin-development@lists.sourceforge.net>;
Sun, 28 Dec 2014 23:55:26 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.194.235.193 with SMTP id uo1mr99840351wjc.105.1419789848159;
Sun, 28 Dec 2014 10:04:08 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.194.188.9 with HTTP; Sun, 28 Dec 2014 10:04:08 -0800 (PST)
Date: Sun, 28 Dec 2014 18:04:08 +0000
X-Google-Sender-Auth: L-23nxgN_9kv4hxpz6yp8nTD24w
Message-ID: <CANEZrP2zxVgeqLZML0UUQUk8aLEZ=oY8pXdunjSq3qfakkdSHA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=089e01419e028e2c62050b4a95b3
X-Spam-Score: 0.3 (/)
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
(mh.in.england[at]gmail.com)
0.8 DATE_IN_PAST_12_24 Date: is 12 to 24 hours before Received: date
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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
0.0 TIME_LIMIT_EXCEEDED Exceeded time limit / deadline
X-Headers-End: 1Y5VAq-0008SU-RJ
Subject: [Bitcoin-development] Bitcoin XT
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, 29 Dec 2014 07:55:48 -0000
--089e01419e028e2c62050b4a95b3
Content-Type: text/plain; charset=UTF-8
Hi there,
I hope everyone who celebrates Christmas is having a relaxing and enjoyable
break! :)
I'd like to announce Bitcoin XT <https://github.com/bitcoinxt/bitcoinxt>, a
patch set on top of Bitcoin Core 0.10rc1 that focuses on enhancements to
the peer to peer protocol. It is reproducibly built with gitian and there
are binaries for Linux, OS X and Windows (code signed). It currently
contains the following two features:
1. Double spend relaying, by Gavin Andresen and Tom Harding. This is
useful for merchants that currently connect to thousands of nodes to spot
double spends, which is wasteful of resources.
2. BIP 64 support (the getutxo message). This is useful for Lighthouse
to render a more helpful GUI.
By running XT you provide additional services to users of the P2P network,
test the features more thoroughly and help build the case for inclusion in
Bitcoin Core.
There is a mailing list for discussion of patch inclusion
<https://groups.google.com/forum/#!forum/bitcoin-xt/>, and another list for
announcements <https://groups.google.com/forum/#!forum/bitcoin-xt-announce>.
Because XT is a patch set the feature branches will be rebased from time to
time. If you branch from them, be aware of that and plan accordingly.
XT nodes advertise themselves by using the getutxo service bit (i.e. bit
2). You can find them by querying a Cartographer, which I will describe in
another email.
A brief note about the goals of this project. The XT project is intended to
provide a friendly environment where [SPV] app developers and merchants can
experiment with new features and explore new directions for the protocol,
if there is demand for that. Those upgrades could then be considered for
inclusion into Core at a later date. I do not expect there to be thousands
of XT users any time soon, but that's OK. Because the patch set contains
features that don't require everyone to opt in (e.g. changes to the
tx/block formats), even just a few nodes can be useful.
Thanks for reading, and have a great new year's eve!
--089e01419e028e2c62050b4a95b3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hi there,<div><br></div><div>I hope everyone who celebrate=
s Christmas is having a relaxing and enjoyable break! :)</div><div><br></di=
v><div>I'd like to announce <a href=3D"https://github.com/bitcoinxt/bit=
coinxt">Bitcoin XT</a>, a patch set on top of Bitcoin Core 0.10rc1 that foc=
uses on enhancements to the peer to peer protocol. It is reproducibly built=
with gitian and there are binaries for Linux, OS X and Windows (code signe=
d). It currently contains the following two features:</div><div><ol><li>Dou=
ble spend relaying, by Gavin Andresen and Tom Harding. This is useful for m=
erchants that currently connect to thousands of nodes to spot double spends=
, which is wasteful of resources.<br><br></li><li>BIP 64 support (the getut=
xo message). This is useful for Lighthouse to render a more helpful GUI.</l=
i></ol><div>By running XT you provide additional services to users of the P=
2P network, test the features more thoroughly and help build the case for i=
nclusion in Bitcoin Core.</div></div><div><br></div><div>There is <a href=
=3D"https://groups.google.com/forum/#!forum/bitcoin-xt/">a mailing list for=
discussion of patch inclusion</a>, and <a href=3D"https://groups.google.co=
m/forum/#!forum/bitcoin-xt-announce">another list for announcements</a>. Be=
cause XT is a patch set the feature branches will be rebased from time to t=
ime. If you branch from them, be aware of that and plan accordingly.</div><=
div><br></div><div>XT nodes advertise themselves by using the getutxo servi=
ce bit (i.e. bit 2). You can find them by querying a Cartographer, which I =
will describe in another email.</div><div><br></div><div><br></div><div><br=
></div><div>A brief note about the goals of this project. The XT project is=
intended to provide a friendly environment where [SPV] app developers and =
merchants can experiment with new features and explore new directions for t=
he protocol, if there is demand for that. Those upgrades could then be cons=
idered for inclusion into Core at a later date. I do not expect there to be=
thousands of XT users any time soon, but that's OK. Because the patch =
set contains features that don't require everyone to opt in (e.g. chang=
es to the tx/block formats), even just a few nodes can be useful.</div><div=
><br></div><div><br></div><div>Thanks for reading, and have a great new yea=
r's eve!</div></div>
--089e01419e028e2c62050b4a95b3--
|
