Bitcoin-Qt / bitcoind version 0.8.6 released

[wumpus]

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

There is a Linux script in contrib/qos that allows throttling the outgoing bandwidth for connections on the Bitcoin network.
For other operating systems, there are likely similar ways to throttle certain applications/ports.

[lindatess]

Yay I can finally combine my smaller amounts of BTC!

[bitmagi]

What is the secret to validating the download with the signature?  I am used to verifying files having a download file say file.tar.gz and then a file.tar.gz.asc and running:

Code:

gpg --verify file.tar.gz.asc 

after importing the authors public key.  However with bitcoin-qt the signature file SHA256SUMS.asc seems to have signature data for all the different versions of bitcoin-qt.  When I import Gavin Andresen's public key and run:

Code:

gpg --verify SHA256SUMS.asc 

I get "Good signature" no matter what.  For instance if I completely delete bitcoin-0.8.6-linux.tar.gz I still get "Good signature"  if I create a blank file called bitcoin-0.8.6-linux.tar.gz I still get "Good signature".  It's as if it isn't actually verifying against the bitcoin-0.8.6-linux.tar.gz file.  What am I doing wrong?

[quone17]

I've looked around and can't find an answer regarding transaction fees paid by qt client.  It seems like sometimes it asks for a trnasaction fee and sometimes it doesn't, and sometimes it says it's going to be one fee and then it's less when I confirm I want to do it.  Finally I have heard you can do slower transactions for less fee but I can't find how to do this.  Thanks

[picobit]

What is the secret to validating the download with the signature? 

First, you check that the downloaded file match the SHA-256 checksum in SHA256SUMS.asc

Code:

shasum -a 256 bitcoin-0.8.6-linux.tar.gz

Then you check that SHA256SUMS.asc itself has not been tampered with

Code:

gpg --verify SHA256SUMS.asc

[virtualmaster]

When will come to the Ubuntu repository ?

[rocket888]

I just want to thank all of you for helping me with these issues. I am very new to this and I feel like the posters here are very helpful! Keep it up!!!

[e4xit]

So I downloaded this for use with OSX 10.9.

I added the app to the Applications folder after verifying the sig. As a shortcut, I copied accross the 'blocks' and 'chainstate' folders from a VM I had running bitcoind on Ubuntu 13.04.

I then opened the Bitcoin-Qt 0.8.6, which 'hung' at the "Opening wallet" splashscreen, for about 24 hours. Luckily I could see in the console debug.log that it was just verifying the blocks, but to go from ~160,000 (where it started) to ~274,000 (where we are now) took 24hours using >700% CPU on an 8 core i7 (Ivy Bridge). Not sure if this is normal behaviour/speed as normally I sync from the network most of the blocks...? I woudl appreciate if anyone would like to comment on this time taken...

It then proceeded to work as expected. I have closed and re-opened the app with no corruption, but have not yet powered the computer off (after safe shutdown) to see if I can then re-open without levelDB corruption.

Will update when I do this, but so far, thanks for this release!

[e4xit]

I've looked around and can't find an answer regarding transaction fees paid by qt client.  It seems like sometimes it asks for a trnasaction fee and sometimes it doesn't, and sometimes it says it's going to be one fee and then it's less when I confirm I want to do it.  Finally I have heard you can do slower transactions for less fee but I can't find how to do this.  Thanks

This may not be entirely accurate for this latest release of Bitcoin-Qt (as it only just came out!) but will explain fees pretty nicely for ya!

http://bitcoinfees.com/

[deepceleron]

but to go from ~160,000 (where it started) to ~274,000 (where we are now) took 24hours using >700% CPU on an 8 core i7 (Ivy Bridge). Not sure if this is normal behaviour/speed as normally I sync from the network most of the blocks...? I woudl appreciate if anyone would like to comment on this time taken...

This is why a new checkpoint would have been nice with this release, full transaction signatures are only verified for transactions in blocks after the checkpoint. I would think that is an unusual amount of CPU time though.

[Daily Anarchist]

When will come to the Ubuntu repository ?

Never. The Bitcoin devs specifically asked package managers not to.

[wumpus]

Never. The Bitcoin devs specifically asked package managers not to.

Correct. It would be great to have the latest version in the package repositories but that's not how it works. Due to stable release policies and such they never keep it up to date.

Use the PPA, at least we have that under control ourselves. https://launchpad.net/~bitcoin/+archive/bitcoin

[aamarket]

thanks to all!
bitcoind seems to be running fine on rk3188 ARM with latest p2pool, compilation failed with Fedora 19x64,will try later.
great work !

[buzybit]

thank you !
just updated with your steps
everything went fine!!
welldone!

[cjp]

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

Looking at the release notes, I don't understand which of the changes fixes a critical bug. Is this one of the OS X specific changes, or is it about a bug that affects all platforms? What is the impact of the bug?

[deepceleron]

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

Looking at the release notes, I don't understand which of the changes fixes a critical bug. Is this one of the OS X specific changes, or is it about a bug that affects all platforms? What is the impact of the bug?

The blockchain getting corrupted and the program crashing when you start it or when you send money are kind of annoying...
This whole thread: https://bitcointalk.org/index.php?topic=337294.0

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

[cjp]

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

Looking at the release notes, I don't understand which of the changes fixes a critical bug. Is this one of the OS X specific changes, or is it about a bug that affects all platforms? What is the impact of the bug?

The blockchain getting corrupted and the program crashing when you start it or when you send money are kind of annoying...
This whole thread: https://bitcointalk.org/index.php?topic=337294.0

OK, so just to be sure: if I understand correctly,

• This bug certainly affects OS X users, and possibly (but probably not) users of other platforms.
• The impact of the bug is that your local copy of the block chain gets corrupted, causing program crashes and generally making it impossible to use the software
• The bug does not lead to a wallet corruption, and it does not allow hackers to do nasty things, such as bitcoin theft or gaining access to your computer

I wanted to know this, because I follow certain procedures when upgrading to a new version, and this will take some time. Since I've been using 0.8.5 without problems on an non-OS X platform for a while, I think I can safely continue to do so, until I've finished the upgrade to 0.8.6.

[wumpus]

There are a few sort-of critical bugs fixed. Transmitting empty transactions and getting banned is ugly. The rare crash-on-send in the GUI can also be quite nasty.

The OSX bug does not affect any other platforms.

[socky]

Nice! Good fixes.

[btc4ever]

anyone have build instructions?

$ git pull

$ make -f makefile.unix
make: makefile.unix: No such file or directory
make: *** No rule to make target `makefile.unix'.  Stop.

$ echo 'WTF?!!!'
WTF?!!!

$ ./configure
-su: ./configure: No such file or directory