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
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1U7srB-0007e0-Ck
for bitcoin-development@lists.sourceforge.net;
Tue, 19 Feb 2013 19:28:01 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.178 as permitted sender)
client-ip=74.125.82.178; envelope-from=gavinandresen@gmail.com;
helo=mail-we0-f178.google.com;
Received: from mail-we0-f178.google.com ([74.125.82.178])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1U7sr6-0007mv-M0
for bitcoin-development@lists.sourceforge.net;
Tue, 19 Feb 2013 19:28:01 +0000
Received: by mail-we0-f178.google.com with SMTP id x48so5933360wey.37
for <bitcoin-development@lists.sourceforge.net>;
Tue, 19 Feb 2013 11:27:50 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.194.123.130 with SMTP id ma2mr21582433wjb.46.1361302070510;
Tue, 19 Feb 2013 11:27:50 -0800 (PST)
Received: by 10.194.176.164 with HTTP; Tue, 19 Feb 2013 11:27:50 -0800 (PST)
Date: Tue, 19 Feb 2013 14:27:50 -0500
Message-ID: <CABsx9T0okOLprP1-S3mOY6mBLF-x-d-3Nc7Ci7ZKDG-2mAeNFA@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=089e012287de58458704d618d637
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
(gavinandresen[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: 1U7sr6-0007mv-M0
Subject: [Bitcoin-development] Bitcoin-Qt / bitcoind version 0.8.0 released
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, 19 Feb 2013 19:28:01 -0000
--089e012287de58458704d618d637
Content-Type: text/plain; charset=ISO-8859-1
Bitcoin-Qt version 0.8.0 are now available from:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.8.0/
This is a major release designed to improve performance and handle the
increasing volume of transactions on the network.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues
How to Upgrade
--------------
If you are running an older version, shut it down. Wait
until it has completely shut down (which might take a few minutes for older
versions), then run the installer (on Windows) or just copy over
/Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (on Linux).
The first time you run after the upgrade a re-indexing process will be
started that will take anywhere from 30 minutes to several hours,
depending on the speed of your machine.
Incompatible Changes
--------------------
This release no longer maintains a full index of historical transaction ids
by default, so looking up an arbitrary transaction using the
getrawtransaction
RPC call will not work. If you need that functionality, you must run once
with -txindex=1 -reindex=1 to rebuild block-chain indices (see below for
more
details).
Improvements
------------
Mac and Windows binaries are signed with certificates owned by the Bitcoin
Foundation, to be compatible with the new security features in OSX 10.8 and
Windows 8.
LevelDB, a fast, open-source, non-relational database from Google, is
now used to store transaction and block indices. LevelDB works much better
on machines with slow I/O and is faster in general. Berkeley DB is now only
used for the wallet.dat file (public and private wallet keys and
transactions
relevant to you).
Pieter Wuille implemented many optimizations to the way transactions are
verified, so a running, synchronized node uses less working memory and does
much less I/O. He also implemented parallel signature checking, so if you
have a multi-CPU machine all CPUs will be used to verify transactions.
New Features
------------
"Bloom filter" support in the network protocol for sending only relevant
transactions to
lightweight clients.
contrib/verifysfbinaries is a shell-script to verify that the binary
downloads
at sourceforge have not been tampered with. If you are able, you can help
make
everybody's downloads more secure by running this occasionally to check PGP
signatures against download file checksums.
contrib/spendfrom is a python-language command-line utility that
demonstrates
how to use the "raw transactions" JSON-RPC api to send coins received from
particular
addresses (also known as "coin control").
New/changed settings (command-line or bitcoin.conf file)
--------------------------------------------------------
dbcache : controls LevelDB memory usage.
par : controls how many threads to use to validate transactions. Defaults
to the number
of CPUs on your machine, use -par=1 to limit to a single CPU.
txindex : maintains an extra index of old, spent transaction ids so they
will be found
by the getrawtransaction JSON-RPC method.
reindex : rebuild block and transaction indices from the downloaded block
data.
New JSON-RPC API Features
-------------------------
lockunspent / listlockunspent allow locking transaction outputs for a
period of time so
they will not be spent by other processes that might be accessing the same
wallet.
addnode / getaddednodeinfo methods, to connect to specific peers without
restarting.
importprivkey now takes an optional boolean parameter (default true) to
control whether
or not to rescan the blockchain for transactions after importing a new
private key.
Important Bug Fixes
-------------------
Privacy leak: the position of the "change" output in most transactions was
not being
properly randomized, making network analysis of the transaction graph to
identify
users' wallets easier.
Zero-confirmation transaction vulnerability: accepting zero-confirmation
transactions
(transactions that have not yet been included in a block) from somebody you
do not
trust is still not recommended, because there will always be ways for
attackers to
double-spend zero-confirmation transactions. However, this release includes
a bug
fix that makes it a little bit more difficult for attackers to double-spend
a
certain type ("lockTime in the future") of zero-confirmation transaction.
Dependency Changes
------------------
Qt 4.8.3 (compiling against older versions of Qt 4 should continue to work)
Thanks to everybody who contributed to this release:
----------------------------------------------------
Alexander Kjeldaas
Andrey Alekseenko
Arnav Singh
Christian von Roques
Eric Lombrozo
Forrest Voight
Gavin Andresen
Gregory Maxwell
Jeff Garzik
Luke Dashjr
Matt Corallo
Mike Cassano
Mike Hearn
Peter Todd
Philip Kaufmann
Pieter Wuille
Richard Schwab
Robert Backhaus
Rune K. Svendsen
Sergio Demian Lerner
Wladimir J. van der Laan
burger2
default
fanquake
grimd34th
justmoon
redshark1802
tucenaber
xanatos
--089e012287de58458704d618d637
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div>Bitcoin-Qt version 0.8.0 are now available from:</div><div>=A0 <a href=
=3D"http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.8.0/">h=
ttp://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.8.0/</a></di=
v>
<div><br></div><div>This is a major release designed to improve performance=
and handle the</div><div>increasing volume of transactions on the network.=
</div><div><br></div><div>Please report bugs using the issue tracker at git=
hub:</div>
<div>=A0 <a href=3D"https://github.com/bitcoin/bitcoin/issues">https://gith=
ub.com/bitcoin/bitcoin/issues</a></div><div><br></div><div>How to Upgrade</=
div><div>--------------</div><div><br></div><div>If you are running an olde=
r version, shut it down. Wait</div>
<div>until it has completely shut down (which might take a few minutes for =
older</div><div>versions), then run the installer (on Windows) or just copy=
over</div><div>/Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (o=
n Linux).</div>
<div><br></div><div>The first time you run after the upgrade a re-indexing =
process will be</div><div>started that will take anywhere from 30 minutes t=
o several hours,</div><div>depending on the speed of your machine.</div>
<div><br></div><div>Incompatible Changes</div><div>--------------------</di=
v><div><br></div><div>This release no longer maintains a full index of hist=
orical transaction ids</div><div>by default, so looking up an arbitrary tra=
nsaction using the getrawtransaction</div>
<div>RPC call will not work. If you need that functionality, you must run o=
nce</div><div>with -txindex=3D1 -reindex=3D1 to rebuild block-chain indices=
(see below for more</div><div>details).</div><div><br></div><div>Improveme=
nts</div>
<div>------------</div><div><br></div><div>Mac and Windows binaries are sig=
ned with certificates owned by the Bitcoin</div><div>Foundation, to be comp=
atible with the new security features in OSX 10.8 and</div><div>Windows 8.<=
/div>
<div><br></div><div>LevelDB, a fast, open-source, non-relational database f=
rom Google, is</div><div>now used to store transaction and block indices. =
=A0LevelDB works much better</div><div>on machines with slow I/O and is fas=
ter in general. Berkeley DB is now only</div>
<div>used for the wallet.dat file (public and private wallet keys and trans=
actions</div><div>relevant to you).</div><div><br></div><div>Pieter Wuille =
implemented many optimizations to the way transactions are</div><div>verifi=
ed, so a running, synchronized node uses less working memory and does</div>
<div>much less I/O. He also implemented parallel signature checking, so if =
you</div><div>have a multi-CPU machine all CPUs will be used to verify tran=
sactions.</div><div><br></div><div>New Features</div><div>------------</div=
>
<div><br></div><div>"Bloom filter" support in the network protoco=
l for sending only relevant transactions to</div><div>lightweight clients.<=
/div><div><br></div><div>contrib/verifysfbinaries is a shell-script to veri=
fy that the binary downloads</div>
<div>at sourceforge have not been tampered with. If you are able, you can h=
elp make</div><div>everybody's downloads more secure by running this oc=
casionally to check PGP</div><div>signatures against download file checksum=
s.</div>
<div><br></div><div>contrib/spendfrom is a python-language command-line uti=
lity that demonstrates</div><div>how to use the "raw transactions"=
; JSON-RPC api to send coins received from particular</div><div>addresses (=
also known as "coin control").</div>
<div><br></div><div>New/changed settings (command-line or bitcoin.conf file=
)</div><div>--------------------------------------------------------</div><=
div><br></div><div>dbcache : controls LevelDB memory usage.</div><div><br>
</div><div>par : controls how many threads to use to validate transactions.=
Defaults to the number</div><div>of CPUs on your machine, use -par=3D1 to =
limit to a single CPU.</div><div><br></div><div>txindex : maintains an extr=
a index of old, spent transaction ids so they will be found</div>
<div>by the getrawtransaction JSON-RPC method.</div><div><br></div><div>rei=
ndex : rebuild block and transaction indices from the downloaded block data=
.</div><div><br></div><div>New JSON-RPC API Features</div><div>------------=
-------------</div>
<div><br></div><div>lockunspent / listlockunspent allow locking transaction=
outputs for a period of time so</div><div>they will not be spent by other =
processes that might be accessing the same wallet.</div><div><br></div>
<div>addnode / getaddednodeinfo methods, to connect to specific peers witho=
ut restarting.</div><div><br></div><div>importprivkey now takes an optional=
boolean parameter (default true) to control whether</div><div>or not to re=
scan the blockchain for transactions after importing a new private key.</di=
v>
<div><br></div><div>Important Bug Fixes</div><div>-------------------</div>=
<div><br></div><div>Privacy leak: the position of the "change" ou=
tput in most transactions was not being</div><div>properly randomized, maki=
ng network analysis of the transaction graph to identify</div>
<div>users' wallets easier.=A0</div><div><br></div><div>Zero-confirmati=
on transaction vulnerability: accepting zero-confirmation transactions</div=
><div>(transactions that have not yet been included in a block) from somebo=
dy you do not</div>
<div>trust is still not recommended, because there will always be ways for =
attackers to</div><div>double-spend zero-confirmation transactions. However=
, this release includes a bug</div><div>fix that makes it a little bit more=
difficult for attackers to double-spend a</div>
<div>certain type ("lockTime in the future") of zero-confirmation=
transaction.</div><div><br></div><div>Dependency Changes</div><div>-------=
-----------</div><div><br></div><div>Qt 4.8.3 (compiling against older vers=
ions of Qt 4 should continue to work)</div>
<div><br></div><div><br></div><div>Thanks to everybody who contributed to t=
his release:</div><div>----------------------------------------------------=
</div><div><br></div><div>Alexander Kjeldaas</div><div>Andrey Alekseenko</d=
iv>
<div>Arnav Singh</div><div>Christian von Roques</div><div>Eric Lombrozo</di=
v><div>Forrest Voight</div><div>Gavin Andresen</div><div>Gregory Maxwell</d=
iv><div>Jeff Garzik</div><div>Luke Dashjr</div><div>Matt Corallo</div><div>
Mike Cassano</div><div>Mike Hearn</div><div>Peter Todd</div><div>Philip Kau=
fmann</div><div>Pieter Wuille</div><div>Richard Schwab</div><div>Robert Bac=
khaus</div><div>Rune K. Svendsen</div><div>Sergio Demian Lerner</div><div>
Wladimir J. van der Laan</div><div>burger2</div><div>default</div><div>fanq=
uake</div><div>grimd34th</div><div>justmoon</div><div>redshark1802</div><di=
v>tucenaber</div><div>xanatos</div><div><br></div>
--089e012287de58458704d618d637--
|