The download directory contains them in a file called SHASUMS.asc:
  http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.0/SHASUMS.asc/download

... which I'll reproduce here just because it is easy:

Yes, it aught to work (for bitcoind, at least-- I haven't tested with bitcoin-qt).  getinfo will tell you if it is working (look at "hashespersec").

You might want to run a testnet-in-a-box, it is 60 time easier to generate blocks on it:
  https://sourceforge.net/projects/bitcoin/files/Bitcoin/testnet-in-a-box/

http://testnet.freebitcoins.appspot.com/  has 11,000 testnet coins available.

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

The major change for this release is a completely new graphical interface that uses the Qt user interface toolkit.

This release include German, Spanish, Spanish-Castilian, Norwegian and Dutch translations. 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

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.

MAJOR BUG FIX  (CVE-2011-4447)

The wallet encryption feature introduced in Bitcoin version 0.4.0 did not sufficiently secure the private keys. An attacker who
managed to get a copy of your encrypted wallet.dat file might be able to recover some or all of the unencrypted keys and steal the
associated coins.

If you have a previously encrypted wallet.dat, the first time you run bitcoin-qt or bitcoind the wallet will be rewritten, Bitcoin will
shut down, and you will be prompted to restart it to run with the new, properly encrypted file.

If you had a previously encrypted wallet.dat that might have been copied or stolen (for example, you backed it up to a public
location) you should send all of your bitcoins to yourself using a new bitcoin address and stop using any previously generated addresses.

Wallets encrypted with this version of Bitcoin are written properly.

Technical note: the encrypted wallet's 'keypool' will be regenerated the first time you request a new bitcoin address; to be certain that the
new private keys are properly backed up you should:

1. Run Bitcoin and let it rewrite the wallet.dat file

2. Run it again, then ask it for a new bitcoin address.
 Bitcoin-Qt: Address Book, then New Address...
 bitcoind: run the 'walletpassphrase' RPC command to unlock the wallet,  then run the 'getnewaddress' RPC command.

3. If your encrypted wallet.dat may have been copied or stolen, send  all of your bitcoins to the new bitcoin address.

4. Shut down Bitcoin, then backup the wallet.dat file.
 IMPORTANT: be sure to request a new bitcoin address before backing up, so that the 'keypool' is regenerated and backed up.

"Security in depth" is always a good idea, so choosing a secure location for the backup and/or encrypting the backup before uploading it is recommended. And as in previous releases, if your machine is infected by malware there are several ways an attacker might steal your bitcoins.

Thanks to Alan Reiner (etotheipi) for finding and reporting this bug.

MAJOR GUI CHANGES

"Splash" graphics at startup that show address/wallet/blockchain loading progress.

"Synchronizing with network" progress bar to show block-chain download progress.

Icons at the bottom of the window that show how well connected you are to the network, with tooltips to display details.

Drag and drop support for bitcoin: URIs on web pages.

Export transactions as a .csv file.

Many other GUI improvements, large and small.

RPC CHANGES

getmemorypool : new RPC command, provides everything needed to construct a block with a custom generation transaction and submit a solution

listsinceblock : new RPC command, list transactions since given block

signmessage/verifymessage : new RPC commands to sign a message with one of your private keys or verify that a message signed by the private key associated with a bitcoin address.

GENERAL CHANGES

Faster initial block download.

---

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

Alan Reiner
Alex B
Alex Waters
Ang Iong Chun
Celil
Chris Howie
Chris Moore
David Joel Schwartz
David Perry
Forrest Voight
Gavin Andresen
Janne Pulkkinen
Jeff Garzik
JoelKatz
Khalahan
Luke Dashjr
Matt Corallo
Misbakh-Soloviev Vadim A
Nils Schneider
Pieter Wuille
Victor Leschuk
Wladimir J. van der Laan
celil-kj
cjdelisle
flower
globalcitizen
gmaxwell
kwaaak
mark
p2k

Yes.

But not being able to download the block-chain sounds like a networking issue that 0.5 is unlikely to fix.

Release Candidate 7 binaries are available at:
  https://sourceforge.net/projects/bitcoin/upload/Bitcoin/bitcoin-0.5.0/test/

Difference between rc6 and rc7 :  rc7 does not remove BDB (Berkeley database) log/* files, because that is causing un-readable wallets on some people's machines (all the reports were from people running 64-bit version of Linux, but that might have just been coincidence-- I could never reproduce the problem in any of my test environments).

What that means:  old private keys can remain in a file on your disk even after wallet encryption, but they will eventually be removed.  Details:

BDB closes the old logfile and opens a new one when it get close to 10megabytes big.

When bitcoin shuts down cleanly, it asks BDB to remove any unused log files, and BDB will remove all but one file from database/log.*

So: if you encrypt your wallet, unencrypted private keys will be in the old part of the log file. But after running for a half a day or so, BDB will close that old log file and open a new one. Then, the next time you restart bitcoin, the old log file containing the unencrypted keys is removed.

This seems like a reasonable compromise between security and safety for now; a better wallet encryption solution for the next version of bitcoin (for example, one that doesn't require shutting down and restarting after encrypting the wallet) is a good idea, but out of scope for this release.

They're not throwing away 0.01 BTC, they just haven't redeemed them yet-- they're using valid-but-strange transactions.

Absolutely no guarantee is made that old, pre-rc6 private keys will not end up unencrypted somewhere on the disk.

There is no guarantee that newly generated, post-rc6 private keys will not end up on the disk, either, although the code tries to keep that from happening (locking memory so it is not swapped to disk, for example).

There should be no files containing unencrypted private keys after rc6 rewrites the wallet, though.

Thanks for helping test!

Why limit it to bitcoin businesses?

Somebody should create a website where you can get a few bitcoins for free, to subsidize adoption.

---

You mean give a significant amount of bitcoins to the 'important' businesses?

Who decides which are 'important' ?

How do you make sure somebody isn't creating fake businesses just to get free bitcoins ?

If you want to subsidize bitcoin businesses and have answers to those questions, then I heartily encourage you to go for it!

I don't have a Linux64-with-GUI machine available to try to debug this, and I've failed to reproduce it on an Ubuntu 10.10 'maverick' server.

If you can, please test (and, if you can, help debug) on 64-bit Linux.  This is the last issue holding up the release.

First: sounds like a bug in Mt Gox's bitcoin address validation code that they should fix.

Second: Do you own the testnet wallet with that address in it? If you do, then it is possible to transfer the public/private keypair from your testnet wallet to your main wallet and recover the coins (but you'll need to use PyWallet or one of sipa's export/import private keys bitcoin branches).

Because the coins are recoverable, you shouldn't expect Mt. Gox to refund the transaction... (otherwise everybody could create testnet versions of their main-net bitcoin addresses, withdraw, and then as Mt Gox to "refund" their "mistake")

If I recall correctly, the courts have ruled that "commercial speech" is not as protected-- so laws that restrict (for example) cigarette ads on television are OK.

Bitcoin transactions would, I think, be very likely to be classified by the courts as non-protected speech, if they were classified as 'speech' at all.

The hosts of Free Talk Live know quite a lot about Bitcoin-- I had lunch with them last year (there's a thread in here somewhere about that....).

RE: "don't emphasize the potential illegal uses" -- mmmm.  Last I heard, Ian was enthusiastic about the Silk Road, so I'd expect it to be part of the conversation.

And I think one of the people associated with the show (I'm being vague because I don't want to reveal something they don't want revealed) lost some bitcoins when MyBitcoin went away, so I'd expect security/trust issues to be raised, too.

Updated to release candidate 6:
 https://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.4.1/test/
 https://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.0/test/

Two changes were made between rc5 and 6:
1) When you encrypt your wallet for the first time, a new keypool is created before Bitcoin-Qt/bitcoind shuts down. This prevents losing bitcoins if you backed up your newly-encrypted wallet, received coins to new addresses, and then later restored from the backup.

There is still a potential problem when you upgrade a previously-encrypted wallet:  in that case, the wallet file is rewritten on startup and will be left with an empty keypool (new keys cannot be written because in this case the code doesn't have your wallet passphrase). The release notes suggest backing up the re-encrypted wallet after generating a new address.

2) Be less aggressive about deleting the database/log.* file(s) on shutdown -- with rc6, they are only deleted if the wallet is successfully encrypted/re-encrypted (to make sure unencrypted private keys are not left in them).

Please report only show-stopper bugs in this thread-- normal bug reports or feature suggestions should go into the github issue tracker:
  https://github.com/bitcoin/bitcoin/issues

Please DO add to this thread if you've done some testing, giving what you tested (0.4.1? 0.5.0 ? win32 exe ?  zip ? linux ?), what operating system you tested on, and if you were testing a fresh install or upgrading (and if upgrading, was your wallet encrypted before?).

Yes, VGA out.

I had grand plans to make this the center of a Linux-powered multimedia center... but after doing nothing with it for a couple of months I think I just won't ever have the time.


This is an Intel Atom D410 -powered little computer, with 1GB of memory and a 250GB hard disk, running a custom version of Linux (easily upgraded to the latest Ubuntu or other Linux distro by booting from a USB stick, though).

Like new in the original box with all the original parts (keyboard, mouse, stand, power cable). New at Amazon: $229

Selling for 90 BTC, I'll pay shipping to the US or Canada.

Good idea.

You might want to set up a testnet-in-a-box environment, so you can pretty easily create blocks yourself to get transactions confirmed quickly:  https://sourceforge.net/projects/bitcoin/files/Bitcoin/testnet-in-a-box/

D'oh!  I was running a -testnet bitcoind....

Never mind.

Neither of those addresses are valid according to my bitcoind:


The checksum in addresses is 4 bytes, so there is a one-in-four-billion chance that a random typo would get you a valid address.