Bitcoin version 0.4 released

[evlew]

Thanks for the hard work.  This should help a lot of people.

[1714056882]

1714056882

[1714056882]

1714056882

[1714056882]

1714056882

[enmaku]

Sadly still not working on W2k 

Are you from the past?

Also, thanks devs!

[bc]

Thank you very much to all of the devs.

[cypherdoc]

this is a Big Day for Bitcoin!  thank you!

[jgarzik]

Please help test, no matter what platform (linux/windows/mac) you are using!

[toffoo]

Wow .. the Mac version actually came out at the same time as the others this time.  This must be a first.  Thanks developers!

[koin]

this image is public domain.

[Bitsky]

Sadly still not working on W2k 

Switch to Linux.  Surely W2K will have enough unpatched security holes that any bitcoins you own will surely get stolen.

It's a server in my home network and already behind a Linux gateway. It's never been compromised and has been running fine needing no attention. I know W2k is old, but this one just works and I don't intend to replace it just because of this update while the old client still works. Especially since the fix should be pretty simple (I already provided details in another thread).

And don't get me started by implying "Linux is safe by default"; for the sake of a civilized discussion, I'll assume you were trolling.

[LoneTrader]

I had some minor troubles after the upgrade, but things seem to be ok now. Just in case someone else runs into the same issue: At first, the 64-bit linux client failed to download any new blocks. The first thing I tried was to start with a new .bitcoin directory; this worked, but I didn't want to re-download the entire chain. Then I tried the new 32-bit client with the original .bitcoin directory, and to my surprise, this worked as well. After downloading a few blocks, I started the 64-bit client again, which continued to download the remaining blocks.

Congratulations on the new release, especially the wallet encryption. Just one feature request (which has been voiced many times, I think): Could you please give some indication of the block chain download status, e.g. a progress indicator? Thanks.

[fornit]

Congratulations on the new release, especially the wallet encryption. Just one feature request (which has been voiced many times, I think): Could you please give some indication of the block chain download status, e.g. a progress indicator? Thanks.

thats already in the qt-gui, so you get it with v0.5 if you dont want to compile that one yourself.

[pent]

Thanks Guys! People, dont forget to donate bitcoins to developers team

[LightRider]

Thanks for the update! I was a bit worried to see the "are you sure you want to encrypt" before the passphrase verification though.

[molecular]

first off: congrats and thanks for the hard work to the devs.

A question:
How does using rpc call "sendtoaddress" work with an encrypted wallet?

[c_k]

Many thanks to all the bitcoin developers, you have solved the immediate problems facing users.

Now on to 0.5 and a pretty GUI!

[enmaku]

And perhaps sipa's mod can make it into the next release so we can all stop using pywallet? No offense to jackjack, it's an excellent tool, but frankly it's a tool that shouldn't exist considering there's been a pull request that duplicates its functionality for quite some time now.

[Pieter Wuille]

first off: congrats and thanks for the hard work to the devs.

A question:
How does using rpc call "sendtoaddress" work with an encrypted wallet?

From the point of RPC, the wallet is either in "locked" or "unlocked" state. You can use the "walletpassphrase" RPC call to unlock it for a limited time. Sendtoaddress and some other commands will fail if the wallet is locked.

[molecular]

first off: congrats and thanks for the hard work to the devs.

A question:
How does using rpc call "sendtoaddress" work with an encrypted wallet?

From the point of RPC, the wallet is either in "locked" or "unlocked" state. You can use the "walletpassphrase" RPC call to unlock it for a limited time. Sendtoaddress and some other commands will fail if the wallet is locked.

Nice, that's a good solution. Thanks for the info, sipa.

[Trader Steve]

+1 

[tvbcof]

I'll be interested in two things, and I'll make some of my own estimates for the fun of it:

1)  Ratio of BTC lost due to forgotten passphrase vs. those to stolen wallet.dat's:
1e) 10/1

2)  First post here from someone needing to know how to get their coins from an encrypted wallet due to forgetting their passphrase:
2e) 3 days

Don't get me wrong...I think this is good an necessary work and I thank the dev team for it and all the other work.  But I do anticipate the encryption contributing to the 'deflationary' nature of the currency

[tsupp4]

You guys are great, thank you for this further step.
Is there a donation adress for the whole developer team or something similar?