Bitcoin-Qt / bitcoind version 0.8.6 released

[wumpus]

Bitcoin-Qt version 0.8.6 final is now available from:

  http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.8.6/

This is a maintenance release to fix a critical bug; we urge all users to upgrade.

Please report bugs using the issue tracker at github:

  https://github.com/bitcoin/bitcoin/issues

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

If you already downloaded 0.8.6rc1 you do not need to re-download. This release is exactly the same.

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).

If you are upgrading from version 0.7.2 or earlier, the first time you
run 0.8.6 your blockchain files will be re-indexed, which will take
anywhere from 30 minutes to several hours, depending on the speed of
your machine.

0.8.6 Release notes
===================

- Default block size increase for miners.
  (see https://gist.github.com/gavinandresen/7670433#086-accept-into-block)

- Remove the all-outputs-must-be-greater-than-CENT-to-qualify-as-free rule for relaying
  (see https://gist.github.com/gavinandresen/7670433#086-relaying)

- Lower maximum size for free transaction creation
  (see https://gist.github.com/gavinandresen/7670433#086-wallet)

- OSX block chain database corruption fixes
  - Update leveldb to 1.13
  - Use fcntl with `F_FULLSYNC` instead of fsync on OSX
  - Use native Darwin memory barriers
  - Replace use of mmap in leveldb for improved reliability (only on OSX)

- Fix nodes forwarding transactions with empty vins and getting banned

- Network code performance and robustness improvements

- Additional debug.log logging for diagnosis of network problems, log timestamps by default

- Fix Bitcoin-Qt startup crash when clicking dock icon on OSX

- Fix memory leaks in CKey::SetCompactSignature() and Key::SignCompact()

- Fix rare GUI crash on send

- Various small GUI, documentation and build fixes

Warning
-------

- There have been frequent reports of users running out of virtual memory on 32-bit systems
  during the initial sync.
  Hence it is recommended to use a 64-bit executable if possible.
  A 64-bit executable for Windows is planned for 0.9.

Note: Gavin Andresen's GPG signing key for SHA256SUMS.asc has been changed from  key id 1FC730C1 to sub key 7BF6E212 (see https://github.com/bitcoin/bitcoin.org/pull/279).

[puck2]

Sourceforge page still reads

Looking for the latest version? Download bitcoin-0.8.5-win32-setup.exe (11.7 MB)

[jgarzik]

Definitely looking for feedback -- good or bad -- from OSX users in particular.  You may have to -reindex to fix the prior corruption issues that impacted earlier versions.

For anyone downloading a fresh copy of the blockchain from scratch, please consider downloading the Bitcoin blockchain torrent.

[EagleTM]

I'm running headless bitcoind on the Electrum server foundry ( http://foundry.electrum.org ) without problems. It all works as expected. It's nice to see some proper timestamps in the debug.log now.

One thing I noticed:
2013-12-09 14:22:59 Bitcoin version v0.8.6.0-g03a7d67-beta ()

-beta is probably not intended for a production release?

[wumpus]

-beta is probably not intended for a production release?

The -beta has been there in every release since the beginning.

[NewLiberty]

-beta is probably not intended for a production release?

The -beta has been there in every release since the beginning.

BITCOIN IS IN BETA
Why do people forget this?

(not only are these the "early days" there are many "early days" to come)

[joecascio]

Definitely looking for feedback -- good or bad -- from OSX users in particular.  You may have to -reindex to fix the prior corruption issues that impacted earlier versions.

For anyone downloading a fresh copy of the blockchain from scratch, please consider downloading the Bitcoin blockchain torrent.

Just downloaded on OSX Snow Leopard. Still doing block verification. Stay tuned.
Does this version expose any of the new Identity work?

[keystroke]

Who signed the SHA256SUMS.asc? Key ID 7BF6E212. Normally they are signed by Gavin's Code Signing key 1FC730C1. I just doubled checked 0.8.5 and that is the case. Why the change in the signing key without any notification?

Also the Windows executable has not been signed by The Foundation. What is going on here?

Edit: Looks like it is a subkey - https://github.com/bitcoin/bitcoin.org/pull/279
I would kindly suggest the release notes be edited to document this change as both differences happening with no warning is a bit scary.

[zimmah]

i'll wait for the 64-bit version.

[joecascio]

Seems to run fine on OSX Snow Leopard. Took a while to sync as I hadn't run old version in a few days, and really burned up the CPU for a good hour doing it. Otherwise all good and shut down without incident as well.

[Zammo]

Is there any chance for future releases that the upload bandwidth used by bitcoind could have a throttle option?

I don't have one of these new fangled VDSL or Cable connections, I have a 8mbit ADSL connection with a staggering 256k upstream. It gives me an upload speed of 38kb/s. Bitcoin-qt sucks up all of that bandwidth which makes even browsing webpages extremely slow and painful, sometimes impossible. It would be nice if there was an option (other than 'exit') so that bitcoin-qt couldn't hijack my internet connection.

[Gavin Andresen]

Bah, I forgot to code-sign the Windows .exe. Expect an updated .exe and SHASUMS soon.

[pc]

Working fine so far on MacOS 10.9 Mavericks. (Though, the prior versions did for me as well.)

And I concur that it'd be nice to have a heads up that the GPG signing key had changed. My GPG downloaded and verified the new key, but it was a little unexpected.

Thanks for all the work you guys put into this experiment!

[dewdeded]

Seems to sync faster on 10.9 OS X, also no problems here.

[keystroke]

Bah, I forgot to code-sign the Windows .exe. Expect an updated .exe and SHASUMS soon.

Thanks Gavin!

[TDB]

When you update the client do your bitcoins on the client stay intact?

[wumpus]

When you update the client do your bitcoins on the client stay intact?

Yes. But as always, backup your wallet.dat regularly to make sure a freak accident doesn't lose your coins.

Edit: Looks like it is a subkey - https://github.com/bitcoin/bitcoin.org/pull/279
I would kindly suggest the release notes be edited to document this change as both differences happening with no warning is a bit scary.

I've added a note to the forum post.

[Nailuj2000]

Version 0.8.6 installed (over 0.8.5) succesfully in OSX 10.8.5 (Hackintosh) with an encrypted wallet. All ok. Thanks!

[bitpop]

Is there any chance for future releases that the upload bandwidth used by bitcoind could have a throttle option?

I don't have one of these new fangled VDSL or Cable connections, I have a 8mbit ADSL connection with a staggering 256k upstream. It gives me an upload speed of 38kb/s. Bitcoin-qt sucks up all of that bandwidth which makes even browsing webpages extremely slow and painful, sometimes impossible. It would be nice if there was an option (other than 'exit') so that bitcoin-qt couldn't hijack my internet connection.

Electrum was made for you. You can also limit the connections from a long time ago.

[deepceleron]

bitcoin y u no checkpoint??

>getblockcountsincecheckpoint
24258