From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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 ; 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: From: Gavin Andresen To: Bitcoin Dev 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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
Bitcoin-Qt version 0.8.0 are now available from:
=A0 h= ttp://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 git= hub:

How to Upgrade
--------------

If you are running an olde= r 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 (o= n Linux).

The first time you run after the upgrade a re-indexing = process will be
started that will take anywhere from 30 minutes t= o several hours,
depending on the speed of your machine.

Incompatible Changes
--------------------

This release no longer maintains a full index of hist= orical transaction ids
by default, so looking up an arbitrary tra= nsaction using the getrawtransaction
RPC call will not work. If you need that functionality, you must run o= nce
with -txindex=3D1 -reindex=3D1 to rebuild block-chain indices= (see below for more
details).

Improveme= nts
------------

Mac and Windows binaries are sig= ned with certificates owned by the Bitcoin
Foundation, to be comp= atible with the new security features in OSX 10.8 and
Windows 8.<= /div>

LevelDB, a fast, open-source, non-relational database f= rom Google, is
now used to store transaction and block indices. = =A0LevelDB works much better
on machines with slow I/O and is fas= ter in general. Berkeley DB is now only
used for the wallet.dat file (public and private wallet keys and trans= actions
relevant to you).

Pieter Wuille = implemented many optimizations to the way transactions are
verifi= ed, 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 tran= sactions.

New Features
------------

"Bloom filter" support in the network protoco= l for sending only relevant transactions to
lightweight clients.<= /div>

contrib/verifysfbinaries is a shell-script to veri= fy that the binary downloads
at sourceforge have not been tampered with. If you are able, you can h= elp make
everybody's downloads more secure by running this oc= casionally to check PGP
signatures against download file checksum= s.

contrib/spendfrom is a python-language command-line uti= lity 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= )
--------------------------------------------------------
<= div>
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=3D1 to = limit to a single CPU.

txindex : maintains an extr= a index of old, spent transaction ids so they will be found
by the getrawtransaction JSON-RPC method.

rei= ndex : 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 witho= ut restarting.

importprivkey now takes an optional= boolean parameter (default true) to control whether
or not to re= scan the blockchain for transactions after importing a new private key.

Important Bug Fixes
-------------------
=

Privacy leak: the position of the "change" ou= tput in most transactions was not being
properly randomized, maki= ng network analysis of the transaction graph to identify
users' wallets easier.=A0

Zero-confirmati= on transaction vulnerability: accepting zero-confirmation transactions
(transactions that have not yet been included in a block) from somebo= dy 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 vers= ions of Qt 4 should continue to work)


Thanks to everybody who contributed to t= his 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 Kau= fmann
Pieter Wuille
Richard Schwab
Robert Bac= khaus
Rune K. Svendsen
Sergio Demian Lerner
Wladimir J. van der Laan
burger2
default
fanq= uake
grimd34th
justmoon
redshark1802
tucenaber
xanatos

--089e012287de58458704d618d637--