From Bitcoin Wiki
Revision as of 22:30, 12 June 2012 by BlueMatt (talk | contribs) (Add 0.4.X)
Jump to: navigation, search

Hashbtc.jpgThis page is a stub. Help by expanding it.

This page aggregates the changelogs that have been posted on the forum for the Bitcoin releases. Note that some download links are not longer valid as highly insecure versions may have been deleted, or links may have changed.



After 0.4.0, all subsequent releases are stable maintenance releases, 0.5.0 is based on 0.4.0.


bitcoind version 0.4.6 is now available for download at: Windows: installer | zip (sig) Source: tar.gz bitcoind and Bitcoin-Qt version are also tagged in git, but it is recommended to upgrade to 0.6.1.

These are bugfix-only releases.

Please report bugs by replying to this forum thread. Note that the 0.4.x wxBitcoin GUI client is no longer maintained nor supported. If someone would like to step up to maintain this, they should contact Luke-Jr.


Version 0.6.0 allowed importing invalid "private keys", which would be unspendable; will now verify the private key is valid, and refuse to import an invalid one Verify status of encrypt/decrypt calls to detect failed padding Check blocks for duplicate transactions earlier. Fixes #1167 Upgrade Windows builds to OpenSSL 1.0.1b Set label when selecting an address that already has a label. Fixes #1080 (Bitcoin-Qt) JSON-RPC listtransactions's from/count handling is now fixed Optimize and fix multithreaded access, when checking whether we already know about transactions Fix potential networking deadlock Proper support for Growl 1.3 notifications Display an error, rather than crashing, if encoding a QR Code failed ( Don't erroneously set "Display addresses" for users who haven't explicitly enabled it (Bitcoin-Qt) Some non-ASCII input in JSON-RPC expecting hexadecimal may have been misinterpreted rather than rejected Missing error condition checking added Do not show green tick unless all known blocks are downloaded. Fixes #921 (Bitcoin-Qt) Increase time ago of last block for "up to date" status from 30 to 90 minutes Show a message box when runaway exception happens (Bitcoin-Qt) Use a messagebox to display the error when -server is provided without providing a rpc password Show error message instead of exception crash when unable to bind RPC port (Bitcoin-Qt) Correct sign message bitcoin address tooltip. Fixes #1050 (Bitcoin-Qt) Removed "(no label)" from QR Code dialog titlebar if we have no label ( Removed an ugly line break in tooltip for mature transactions ( Add missing tooltip and key shortcut in settings dialog (part of #1088) (Bitcoin-Qt) Work around issue in boost::program_options that prevents from compiling in clang Fixed bugs occurring only on platforms with unsigned characters (such as ARM). Rename to .sh as it is a shell script. Fixes #1099 (Bitcoin-Qt) Various trivial internal corrections to types used for counting/size loops and warnings


(No known forum post.)


Bitcoin version 0.4.4 is now available for download at:

This is a bugfix-only release based on 0.4.0.

Please note that the wxBitcoin GUI client is no longer maintained nor supported. If someone would like to step up to maintain this, they should contact Luke-Jr.

Please report bugs for the daemon only using the issue tracker at github:

Stable source code is hosted at Gitorious:


Limit the number of orphan transactions stored in memory, to prevent a potential denial-of-service attack by flooding orphan transactions. Also never store invalid transactions at all. Fix possible buffer overflow on systems with very long application data paths. This is not exploitable. Resolved multiple bugs preventing long-term unlocking of encrypted wallets (issue #922). Only send local IP in "version" messages if it is globally routable (ie, not private), and try to get such an IP from UPnP if applicable. Reannounce UPnP port forwards every 20 minutes, to workaround routers expiring old entries, and allow the -upnp option to override any stored setting. Various memory leaks and potential null pointer deferences have been fixed. Several shutdown issues have been fixed. Check that keys stored in the wallet are valid at startup, and if not, report corruption. Various build fixes. If no password is specified to bitcoind, recommend a secure password. Update hard-coded fallback seed nodes, choosing recent ones with long uptime and versions at least 0.4.0. Add checkpoint at block 168,000.


bitcoind version 0.4.3 is now available for download at: (until Gavin uploads to SourceForge)

This is a bugfix-only release based on 0.4.0.

Please note that the wxBitcoin GUI client is no longer maintained nor supported. If someone would like to step up to maintain this, they should contact Luke-Jr.

Please report bugs for the daemon only using the issue tracker at github:

Stable source code is hosted at Gitorious:


Cease locking memory used by non-sensitive information (this caused a huge performance hit on some platforms, especially noticable during initial blockchain download). Fixed some address-handling deadlocks (client freezes). No longer accept inbound connections over the internet when Bitcoin is being used with Tor (identity leak). Use the correct base transaction fee of 0.0005 BTC for accepting transactions into mined blocks (since 0.4.0, it was incorrectly accepting 0.0001 BTC which was only meant to be relayed). Add new DNS seeds (maintained by Pieter Wuille and Luke Dashjr).


(No known forum post.)


Bitcoin version 0.4.1 is now available for download at:

This is a bugfix only release based on 0.4.0.

Please report bugs by replying to this forum thread.

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 wxbitcoin 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.

wxBitcoin: new address visible on main window
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.


Bitcoin version 0.4.0 is now available for download at:

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.

Notable bug fixes from version 0.3.24:

Fix several bitcoin-becomes-unresponsive bugs due to multithreading deadlocks.

Optimize database writes for large (lots of inputs) transactions (fixes a potential denial-of-service attack)

Wallet Encryption

Bitcoin supports native wallet encryption so that people who steal your wallet file don't automatically get access to all of your Bitcoins. In order to enable this feature, choose "Encrypt Wallet" from the Options menu. You will be prompted to enter a passphrase, which will be used as the key to encrypt your wallet and will be needed every time you wish to send Bitcoins. If you lose this passphrase, you will lose access to spend all of the bitcoins in your wallet, no one, not even the Bitcoin developers can recover your Bitcoins. This means you are responsible for your own security, store your passphrase in a secure location and do not forget it.

Remember that the encryption built into bitcoin only encrypts the actual keys which are required to send your bitcoins, not the full wallet. This means that someone who steals your wallet file will be able to see all the addresses which belong to you, as well as the relevant transactions, you are only protected from someone spending your coins.

It is recommended that you backup your wallet file before you encrypt your wallet. To do this, close the Bitcoin client and copy the wallet.dat file from ~/.bitcoin/ on Linux, /Users/(user name)/Application Support/Bitcoin/ on Mac OSX, and %APPDATA%/Bitcoin/ on Windows (that is /Users/(user name)/AppData/Roaming/Bitcoin on Windows Vista and 7 and /Documents and Settings/(user name)/Application Data/Bitcoin on Windows XP). Once you have copied that file to a safe location, reopen the Bitcoin client and Encrypt your wallet. If everything goes fine, delete the backup and enjoy your encrypted wallet. Note that once you encrypt your wallet, you will never be able to go back to a version of the Bitcoin client older than 0.4.

Keep in mind that you are always responsible for your own security. All it takes is a slightly more advanced wallet-stealing trojan which installs a keylogger to steal your wallet passphrase as you enter it in addition to your wallet file and you have lost all your Bitcoins. Wallet encryption cannot keep you safe if you do not practice good security, such as running up-to-date antivirus software, only entering your wallet passphrase in the Bitcoin client and using the same passphrase only as your wallet passphrase.

See the doc/README file in the bitcoin source for technical details of wallet encryption.



Bitcoin v0.3.24 is now available for download at

This is another bug fix release. We had hoped to have wallet encryption ready for release, but more urgent fixes for existing clients were needed -- most notably block download problems were getting severe. Wallet encryption is ready for testing at for the git-savvy, and hopefully will follow shortly in the next release, v0.4.

Notable fixes in v0.3.24, and the main reasons for this release:

F1) Block downloads were failing or taking unreasonable amounts of time to complete, because the increased size of the block chain was bumping up against some earlier buffer-size DoS limits.

F2) Fix crash caused by loss/lack of network connection.

Notable changes in v0.3.24:

C1) DNS seeding enabled by default.

C2) UPNP enabled by default in the GUI client. The percentage of bitcoin clients that accept incoming connections is quite small, and that is a problem. This should help. bitcoind, and unofficial builds, are unchanged (though we encourage use of "-upnp" to help the network!)

C3) Initial unit testing framework. Bitcoin sorely needs automated tests, and this is a beginning. Contributions welcome.

C4) Internal wallet code cleanup. While invisible to an end user, this change provides the basis for v0.4's wallet encryption.


Win32, Linux, MacOSX and source releases for bitcoin v0.3.23 have been uploaded to

This is another quick bugfix release, trying to deal with the influx of new bitcoin users.

Main items of note:

  • P2P connect-to-node logic changed to reduce timeout a bit. The network saw a huge influx of new users, who do not permit incoming connections. This change is a short-term hack, to more quickly hunt for useful P2P connections. Better "leaf node" logic is in the works, but this should let us limp along until then. One may use -upnp to properly forward ports, and help the network.
  • Transaction fee reduced to 0.0005 for new transactions
  • Client will relay transactions with fees as low as 0.0001 BTC


Download URL:

This is largely a bugfix and TX fee schedule release. We also hope to make 0.3.23 a quick release, to fix problems that the network has seen due to explosive growth in the past week.

Notable changes:

  • Client will accept and relay TX's with 0.0005 BTC fee schedule (users still pay 0.01 BTC per kb, until next version)
  • Non-standard transactions accepted on testnet
  • Source code tree reorganized (prep for autotools build)
  • Remove "Generate Coins" option from GUI, and remove 4way SSE miner. Internal reference CPU miner remains available, but users are directed to external miners for best hash production.
  • IRC is overflowing. Client now bootstraps to channels #bitcoin00 - #bitcoin99
  • DNS names now may be used with -addnode, -connect (requires -dns to enable)

RPC changes:

  • 'listtransactions' adds 'from' param, for range queries
  • 'move' may take account balances negative
  • 'settxfee' added, to manually set TX fee


Binaries for Bitcoin version 0.3.21 are available at:

Changes and new features from the 0.3.20 release include:

  • Universal Plug and Play support. Enable automatic opening of a port for incoming connections by running bitcoin or bitcoind with the - -upnp=1 command line switch or using the Options dialog box.
  • Support for full-precision bitcoin amounts. You can now send, and bitcoin will display, bitcoin amounts smaller than 0.01. However, sending fewer than 0.01 bitcoins still requires a 0.01 bitcoin fee (so you can send 1.0001 bitcoins without a fee, but you will be asked to pay a fee if you try to send 0.0001).
  • A new method of finding bitcoin nodes to connect with, via DNS A records. Use the -dnsseed option to enable.

For developers, changes to bitcoin's remote-procedure-call API:

  • New rpc command "sendmany" to send bitcoins to more than one address in a single transaction.
  • Several bug fixes, including a serious intermittent bug that would sometimes cause bitcoind to stop accepting rpc requests.
  • -logtimestamps option, to add a timestamp to each line in debug.log.
  • Immature blocks (newly generated, under 120 confirmations) are now shown in listtransactions.[10]

The maxsendbuffer bug ( clients not being able to download the block chain from other clients) was only going to get worse as people upgraded, so I cherry-picked the bug fix and created a minor release yesterday.

The Amazon Machine Images I used to do the builds are available:

 ami-38a05251   Bitcoin-v0.3.20.2 Mingw    (Windows; Administrator password 'bitcoin development')
 ami-30a05259   Bitcoin_0.3.20.2 Linux32
 ami-8abc4ee3   Bitcoin_0.3.20.2 Linux64

(mac build will be done soon)

If you have already downloaded version, please either add this to your bitcoin.conf file:


... or download the new version.

(No known forum post.)


Please checkout the git integration branch from:

... and help test. The new features that need testing are:

Bug fixes that also need testing:

This needs more testing on Windows! Please drop me a quick private message, email, or IRC message if you are able to do some testing. If you find bugs, please open an issue at:


There's more work to do on DoS, but I'm doing a quick build of what I have so far in case it's needed, before venturing into more complex ideas. The build for this is version 0.3.19.

- Added some DoS controls As Gavin and I have said clearly before, the software is not at all resistant to DoS attack. This is one improvement, but there are still more ways to attack than I can count.

I'm leaving the -limitfreerelay part as a switch for now and it's there if you need it.

- Removed "safe mode" alerts "safe mode" alerts was a temporary measure after the 0.3.9 overflow bug. We can say all we want that users can just run with "-disablesafemode", but it's better just not to have it for the sake of appearances. It was never intended as a long term feature. Safe mode can still be triggered by seeing a longer (greater total PoW) invalid block chain.



  • Fixed a wallet.dat compatibility problem if you downgraded from 0.3.17 and then upgraded again
  • IsStandard() check to only include known transaction types in blocks
  • Jgarzik's optimisation to speed up the initial block download a little

The main addition in this release is the Accounts-Based JSON-RPC commands that Gavin's been working on (more details at

  • getaccountaddress
  • sendfrom
  • move
  • getbalance
  • listtransactions


Version 0.3.17 is now available.


  • new getwork, thanks m0mchil
  • added transaction fee setting in UI options menu
  • free transaction limits
  • sendtoaddress returns transaction id instead of "sent"
  • getaccountaddress <account>

The UI transaction fee setting was easy since it was still there from 0.1.5 and all I had to do was re-enable it.

The accounts-based commands: move, sendfrom and getbalance <account> will be in the next release. We still have some more changes to make first.


Never released.


  • paytxfee switch is now per KB, so it adds the correct fee for large transactions
  • sending avoids using coins with less than 6 confirmations if it can
  • BitcoinMiner processes transactions in priority order based on age of dependencies
  • make sure generation doesn't start before block 74000 downloaded
  • bugfixes by Dean Gores
  • testnet, keypoololdest and paytxfee added to getinfo


Version 0.3.14 is now available


  • Key pool feature for safer wallet backup

Gavin Andresen:

  • TEST network mode with switch -testnet
  • Option to use SSL for JSON-RPC connections on unix/osx
  • validateaddress RPC command


  • Russian translation


Version 0.3.13 is now available. You should upgrade to prevent potential problems with 0/unconfirmed transactions. Note: 0.3.13 prevents problems if you haven't already spent a 0/unconfirmed transaction, but if that already happened, you need


  • Don't count or spend payments until they have 1 confirmation.
  • Internal version number from 312 to 31300.
  • Only accept transactions sent by IP address if -allowreceivebyip is specified.
  • Dropped DB_PRIVATE Berkeley DB flag.
  • Fix problem sending the last cent with sub-cent fractional change.
  • Auto-detect whether to use 128-bit 4-way SSE2 on Linux.

Gavin Andresen:

  • Option -rpcallowip= to accept json-rpc connections from another machine.
  • Clean shutdown on SIGTERM on Linux.


(Thanks Laszlo for the Mac OSX build!)

Note: The SSE2 auto-detect in the Linux 64-bit version doesn't work with AMD in 64-bit mode. Please try this instead and let me know if it gets it right:

You can still control the SSE2 use manually with -4way and -4way=0.

Version (SVN rev 161) has improvements for the case where you already had 0/unconfirmed transactions that you might have already spent. Here's a Windows build of it:


Version 0.3.12 is now available.


  • json-rpc errors return a more standard error object. (thanks to Gavin Andresen)
  • json-rpc command line returns exit codes.
  • json-rpc "backupwallet" command.
  • Recovers and continues if an exception is caused by a message you received. Other nodes shouldn't be able to cause an exception, and it hasn't happened before, but if a way is found to cause an exception, this would keep it from being used to stop network nodes.

If you have json-rpc code that checks the contents of the error string, you need to change it to expect error objects of the form {"code":<number>,"message":<string>}, which is the standard. See this thread: