Bitcoin-Qt, bitcoind version 0.5.1 released

[Gavin Andresen]

Bitcoin version 0.5.1 is now available for download at:
  http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.1/

This is a bugfix-only release.

This release includes 13 translations, including 5 new translations:
Italian, Hungarian, Ukranian, Portuguese (Brazilian) and Simplified Chinese.
More translations are welcome; join the project at Transifex if you can help:
  https://www.transifex.net/projects/p/bitcoin/

Please report bugs using the issue tracker at github:
  https://github.com/bitcoin/bitcoin/issues

Project source code is hosted at github; we are no longer
distributing .tar.gz files here, you can get them
directly from github:
 https://github.com/bitcoin/bitcoin/tarball/v0.5.1  # .tar.gz
 https://github.com/bitcoin/bitcoin/zipball/v0.5.1  # .zip

For Ubuntu users, there is a new ppa maintained by Matt Corallo which
you can add to your system so that it will automatically keep
bitcoin up-to-date.  Just type
 sudo apt-add-repository ppa:bitcoin/bitcoin
in your terminal, then install the bitcoin-qt package.

BUG FIXES
---------

Re-enable SSL support for the JSON-RPC interface (it was unintentionally
disabled for the 0.5.0 release binaries).

The code that finds peers via "dns seeds" no longer stops bitcoin startup
if one of the dns seed machines is down.

Tooltips on the transaction list view were rendering incorrectly (as black boxes
or with a transparent background).

Prevent a denial-of-service attack involving flooding a bitcoin node with
orphan blocks.

The wallet passphrase dialog now warns you if the caps lock key was pressed.

Improved searching in addresses and labels in bitcoin-qt.

===============================

Thanks to everybody who contributed code or helped test this release:

Alex B
Clark Gaebel
Dylan Noblesmith
Gavin Andresen
Luke Dashjr
Matt Corallo
Michael Hendricks
Nick Bosma
Nils Schneider
Wladimir J. van der Laan

[1714220595]

1714220595

[1714220595]

1714220595

[1714220595]

1714220595

[1714220595]

1714220595

[1714220595]

1714220595

[Azrael_PT]

Hi
No Portuguese (European)?

[cypherdoc]

did u get that reversion to a previous password fixed?

also will the new version overwrite previous versions?  0.5 left 0.4 on my win 7 version and occasionally 0.4 opens up automatically.  interestingly its wallet is encrypted and i can send btc's with the password from within 0.4

[damnek]

Thanks for all the hard work, Gavin (and all the other developers)!

[pc]

GPG signature bitcoin-0.5.1-macosx.dmg.asc tells me that bitcoin-0.5.1-macosx.dmg is correctly signed by key BE38D3A8, but on bitcoin.org the "PGP" link next to Gavin's name gives me a public key 1FC730C1. I just wanted to confirm that both of those keys in fact belong to Gavin. (This is my first time attempting to verify a Bitcoin download via GPG instead of just the SHA hash, so it's quite possible I'm doing something wrong here, too.)

[nmat]

Thanks to everyone who was involved in this.

[hugolp]

I recently tried version 5 coming from version 3 and I want to congratulate whoever made the client eat a lot less RAM. Big improvement.

[Pieter Wuille]

did u get that reversion to a previous password fixed?

Explain?

[cypherdoc]

did u get that reversion to a previous password fixed?

Explain?

in v0.4 i changed my pw once.  then i installed 0.5 and encrypted the wallet.  the new pw wouldn't work; i had to use the original pw.

[Gavin Andresen]

GPG signature bitcoin-0.5.1-macosx.dmg.asc tells me that bitcoin-0.5.1-macosx.dmg is correctly signed by key BE38D3A8, but on bitcoin.org the "PGP" link next to Gavin's name gives me a public key 1FC730C1. I just wanted to confirm that both of those keys in fact belong to Gavin.

Yes, those are both my PGP keys. I generated a new, stronger key yesterday (1FC7...) that I intend to use for code signing for the next release. I thought I'd changed the gavinandresen.asc file on bitcoin.org to contain both keys, but it looks like I didn't (or pgp/gpg doesn't allow more than one key in the .asc file; I was disappointed to learn that gpg doesn't support putting multiple signatures in an .asc file...)

[proudhon]

I haven't run a bitcoin client in a few months now.  I just ran this one and I'm impressed with the progress.  It still takes a while to get the whole blockchain but not nearly as long as it did in the clients I ran in the past.  Also, usability has improved a lot.  Nice work.

[molecular]

Awesome GUI!

I must admit I've not been looking at bitcoins gui for many months (since 0.3.x).

Congrats to all devs/testers and whoever else made this nice release possible.

Also: cool, I'm now a millionaire (in µBTC)

[cypherdoc]

0.4 still won't go away!  automatically loads in my tray despite 0.51 download.

[cypherdoc]

i hadn't backed up my wallet for a while and just noticed that there is now a wallet.dat and a wallet.dat.rewrite in my Bitcoin folder.  which is the real private key wallet that needs to be backed up?

[Bitsky]

Runs fine on XP, which is good for occasional use.
Sadly still fails on W2k, which is bad for constant use.

Maybe it would make sense to add an option to pause the blockchain download. That might come in handy during the initial download, when you sometimes need all resources for something else.

[ovidiusoft]

0.5.1 works ok for me. Compiled from source, Ubuntu Linux 11.04, 64 bit.

[dlb76]

updated to 0.5.1-beta
Thanks for fixing tooltips on the transaction list view!

[molecular]

Runs fine on XP, which is good for occasional use.
Sadly still fails on W2k, which is bad for constant use.

Maybe it would make sense to add an option to pause the blockchain download. That might come in handy during the initial download, when you sometimes need all resources for something else.

You can just quit the client and start it again, no problem. You'll have some overhead due to the network reconnect, but it's negligible, I'd say.

[BrightAnarchist]

i hadn't backed up my wallet for a while and just noticed that there is now a wallet.dat and a wallet.dat.rewrite in my Bitcoin folder.  which is the real private key wallet that needs to be backed up?

I believe .rewrite is the old wallet, which ideally should be "rewritten" over since it may hold unencrypted private keys as a result of a bug in the 0.4 wallet encryption code. Ideally though if you used the built in encryption prior to 0.5 you should transfer your coins to a new wallet in case the old one has leaked.

[mcorlett]

I thought I'd changed the gavinandresen.asc file on bitcoin.org to contain both keys, but it looks like I didn't (or pgp/gpg doesn't allow more than one key in the .asc file; I was disappointed to learn that gpg doesn't support putting multiple signatures in an .asc file...)

The Apache Foundation uses something they call the KEYS file: http://www.apache.org/dev/release-signing#keys-policy