Bitcoin Forum

Linux and Windows and Mac binaries are available at sourceforge:
  http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.4.0/test/

And HTTPS download from the Amazon Cloudfront content distribution network:
 https://d24z2fz21y4fag.cloudfront.net/downloads/bitcoin/bitcoin/bitcoin-0.4rc2-win32-setup.exe
 https://d24z2fz21y4fag.cloudfront.net/downloads/bitcoin/bitcoin/bitcoin-0.4rc2-win32.zip
 https://d24z2fz21y4fag.cloudfront.net/downloads/bitcoin/bitcoin/bitcoin-0.4rc2-macosx.dmg
 https://d24z2fz21y4fag.cloudfront.net/downloads/bitcoin/bitcoin/bitcoin-0.4rc2-linux.tar.gz

The d24z.... downloads are an experiment; I like that they're https, I don't like the obscure d24z... URL (that's actually github's CloudFront id; I asked, and they have no objections to linking directly to the https version of the downloads).

Executive summary release notes:

The main feature in this release is wallet private key encryption;
you can set a passphrase that must be entered before sending coins.
See below for more information; if you decide to encrypt your wallet,
WRITE DOWN YOUR PASSPHRASE AND PUT IT IN A SECURE LOCATION. If you
forget or lose your wallet passphrase, you lose your bitcoins.
Previous versions of bitcoin are unable to read encrypted wallets,
and will crash on startup if the wallet is encrypted.

Also note: bitcoin version 0.4 uses a newer version of Berkeley DB
(bdb version 4.8) than previous versions (bdb 4.7). If you upgrade
to version 0.4 and then revert back to an earlier version of bitcoin
the it may be unable to start because bdb 4.7 cannot read bdb 4.8
"log" files.

Go Bitcoin Dev Team Go!

That is great news, woohoo!

Windows links are giving me

https://i.imgur.com/MrBbm.png

Using windows7x64, chrome

0.4rc2 is working a lot better than 0.3.24 on my OSX Snow Leopard. It seems to write a lot less data continuously to disk (which made .24 almost impossible to use) and for some reason I'm getting a lot more (8+) connections now vs just 8 before (same router, UPnP support switched on in both versions). Both of these things might play a part in that blocks now seem to be downloaded much quicker than before as well.

Oh wallet encryption? Haven't tried that out yet ;)

I am also not able to not download the Mac os version but thank you for developing Bitcoin, I will try it as soon as it works.

Edit: Okay one version @ sourceforge works. I will test it
------------

I found a Bug on the mac version.
Settings->Encrypt Wallet-> Cancel: Error: The supplied passphrase was too short.

No matter if I enter a valid keyphrase or not. Seems that it does not really cancel.

As in the versions before it takes a very long long time to start and close the client.

Tested with Opera on linux here, all 4 cloudfront links give access denied.
links on https://github.com/bitcoin/bitcoin/downloads - same result.
Downloads from http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.4.0/test/ work...

Ahh, silly me, I got around the errors by right-clicking and 'save link as'.

Edit:  But unable to open.  The windows.exe is reported as a 16bit program, and the .zip looks corrupt

Yeah it's because while you get a file when right-clicking it's still the same error message and not the actual program.

After start there was almost exactly 60 seconds of "nothing".

The delay was there in the previous versions, but now it got even bigger.

This delay can easily cause "wtf?" moment for people who don't know how to open the task manager and make sure that the process has started.

Isn't it possible to show interface first, and then do the startup work, probably in a separate thread? You have 14 of them already! Why, by the way?

--

70 Mb of memory? For a program that is supposed to be constantly running?

--

Scary thing is that it tried to install some sort of driver 3 times. "WMIApSrv" and 2 "unknown".

After I denied, it started and seems to be working Ok. Do you run some sort of performance analysis?

Maybe that's why so much memory and so many threads...

--

HDD activity is pretty much the same. If there is a difference, it's not noticeable. Still annoying.

Aha, but it ended noticeably sooner. That's good.

--

Having a single password field for encrypting the wallet made me uneasy. Maybe it's better to show 2 fields from the start, rather than confirm later.

Wallet encryption seems working Ok.

--

Resizing "Send Coins" dialog produces bad results. Why is it resizable? Address Book and Transaction Details dialogs are resizable to zero. That's not good.

Main window is also resizable to zero - that's even worse!

--

List of transactions cannot be sorted by clicking on the column headers.

--

What's the difference between "All Transactions" and "Sent/Received"? Isn't sending and receiving all you can do? :)

That's it so far.

I am unable to run this in Windows Server 2008. It opens up for a few seconds and then just shuts down. Event log viewer shows the following error

"Faulting application name: bitcoin.exe, version: 0.0.0.0, time stamp: 0x4d44aa00"

Unforunately it won't start in W2k (I know it's an old OS, but that's what my Intranet server is running).

I reported that for version 0.3.21 and think Matt already took a closer look into it: https://bitcointalk.org/index.php?topic=24841.0

Agree on some points raised by AlexZ. Starting the program on a fast computer with an SSD takes like 10-20 seconds, after which the window can be unresponsive for some time. Though the start up has always been slow. Not sure how it compares to previous version.

The encryption thing was scary indeed, I thought I was going to get away by typing my pass once :)

I did not notice it trying to install some drivers.. on Windows 7.

RE: long delay, no window on startup:  will be made much better by the QT splash screens in bitcoin 0.5.
RE: lots of GUI bugs: whole rafts of wxwidgets-related bugs will go away with the switch to QT in bitcoin 0.5.

RE: incompatible on older version of windows: I don't know nuthin about windows compatibility, somebody want to volunteer to investigate?  Is bitcoin 0.4 less compatible for some reason than 0.3.24 was?  (shouldn't be...)

https://i.imgur.com/5fcro.png

I get that on Windows 7 64bit. The Send and Cancel buttons are tiny.

Is there a way to un-encrypt the wallet? I guess importing addresses won't work with the encrypted wallet, right?

Hi!

 When I close the Bitcoin, e see:



 I'm using Ubuntu Natty 11.04 32 bits.

Thanks!
Thiago

I'm still getting this segfault in 0.40rc2, but it's gone in bitcoin-qt that is built on 0.40rc1.

Kudos Gavin and Dev Team!

Matt mentioned that it's related to MinGW and the upnp library. I don't mind testing builds on W2k.

I have updated the monitoring site:
http://bitcoinstatus.rowit.co.uk/versions.html

Seem to be 44 copies running now.

Is there a way to un-encrypt the wallet?

No.

Why not? I don't remember. Why would you want to un-encrypt it?  (I ask because if you want to save an unencrypted backup then maybe a better feature would be "backup wallet" with an option to backup encrypted or unencrytped)

To import addresses into it.

I have a backup, can there be any problems if I just overwrite the encrypted wallet with the backup? I didn't have any new transactions.

Private key import/export (which is ready for merging, but not yet in 0.4) is already rebased against wallet crypto, and will decrypt private keys on export, and encrypt them on import.

Also, backups work as before: even encrypted wallets contain reserve keys, and as long as you didn't use them all up, restoring a backup shouldn't be any problem.

I've not done much testing yet but have had no serious problems with rc2 yet.

I only found one minor issue.  As has been mentioned before, the 'Cancel' buttons of many of the dialogue boxes which ask for a password are not handled properly.  When encrypting a wallet or changing the password the cancel button always gives an error.  Also, when supplying a password for a payment or for creating a new address the cancel button picks up the "please supply a password" information box which I assume is intended for the case of selecting 'OK' with an empty password field.

The information boxes and warnings given when encrypting a wallet or changing a password are particularly well done.  I'm sure we agree that this aspect of the user interface is perhaps the most important.  I thought it would be good to mention that wallets cannot easily be decrypted but this would make the confirmation dialogue for wallet encryption too long.  One thing I found odd was that the confirmation dialogue was placed between asking for a password and confirming the password.  The first time I came to the dialogue I was worried that the password I'd supplied contained a typo.

Among other things I've created some new addresses, transferred BTC in and out, restored an unencrypted backup.  I've not managed to break the software and everything seems to work as it should.

Do you accept donations for client development Gavin?