Please help sanity test: version 0.5.1

[Gavin Andresen]

Please help sanity test version 0.5.1 release candidate 1.

Why a version 0.5.1 ?  To fix the bugs listed below before starting on 0.6 release candidate testing.

After doing some testnet testing to make sure it works properly, I plan on using the "alert" system built in to the client to warn 0.4 users that if they have an encrypted wallet they need to upgrade to be secure.

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

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

[1713961342]

1713961342

[1713961342]

1713961342

[1713961342]

1713961342

[finway]

Looking nice!

[nelisky]

A little off topic, but when did the transaction dates stop being shown from the block timestamp and started being the timestamp at which the block was received? This bugs me because I do mental averages of generation, and only start the client every now and then, which then proceeds to download the blockchain pinning all new transactions under more or less the same date and time, i.e. now.

This still happens with 0.5.1, don't know if a bug or feature, it started somewhere on the 0.4 series and I always forget to report...

Other than that, looks very stable to me, but I've only done 'normal' usage, no real hard core testing.

[fornit]

works on windows 7, 64bit.

nice to see a bugfix release so fast after 0.5. 
please please please sneak in a fix for the autostart option.
thats very likely easy to fix and can keep quite a few people from running bitcoin all the time.

[pusle]

works on good old XP 32bit  *pet*pet* 

[Gavin Andresen]

I'll be uploading Release Candidate 2 binaries this afternoon, with two bug fixes from RC1 (text was being truncated in the wallet passphrase dialog box, and previous versions of bitcoin-qt did not display "alert" messages).

[Luke-Jr]

Also tagged are 0.4.2rc1 (bitcoind only) and 0.5.0.1rc2 (bitcoind and Bitcoin-Qt). Note that I do not intend to maintain 0.5.0.x very long.

[randomguy7]

I found a bug but while running the most up to date code from github (running on linux), I assume it's also in 0.5.1.
It's the keypool-bug which afaik was fixed in an earlier version. If I start the client with -keypool=<whatever>, I have to create a new address to actually get the keypool increased.

[btc_artist]

Nice to see this release so soon after the 0.5 release.

[btc_artist]

The sweep/import privkey posts were moved here: https://bitcointalk.org/index.php?topic=54603.0

[kyoo]

A little off topic, but when did the transaction dates stop being shown from the block timestamp and started being the timestamp at which the block was received? This bugs me because I do mental averages of generation, and only start the client every now and then, which then proceeds to download the blockchain pinning all new transactions under more or less the same date and time, i.e. now.

This still happens with 0.5.1, don't know if a bug or feature, it started somewhere on the 0.4 series and I always forget to report...

Other than that, looks very stable to me, but I've only done 'normal' usage, no real hard core testing.

For me this also seems like a bug. If this should be a feature, at least it should be possible to display both sorts of dates.

[Luke-Jr]

A little off topic, but when did the transaction dates stop being shown from the block timestamp and started being the timestamp at which the block was received? This bugs me because I do mental averages of generation, and only start the client every now and then, which then proceeds to download the blockchain pinning all new transactions under more or less the same date and time, i.e. now.

This still happens with 0.5.1, don't know if a bug or feature, it started somewhere on the 0.4 series and I always forget to report...

Other than that, looks very stable to me, but I've only done 'normal' usage, no real hard core testing.

For me this also seems like a bug. If this should be a feature, at least it should be possible to display both sorts of dates.

https://bitcointalk.org/index.php?topic=54527.0