release-notes-0.6.0.md
1 Bitcoin version 0.6.0 is now available for download at: 2 http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.6.0/test/ 3 4 This release includes more than 20 language localizations. 5 More translations are welcome; join the 6 project at Transifex to help: 7 https://www.transifex.net/projects/p/bitcoin/ 8 9 Please report bugs using the issue tracker at github: 10 https://github.com/bitcoin/bitcoin/issues 11 12 Project source code is hosted at github; we are no longer 13 distributing .tar.gz files here, you can get them 14 directly from github: 15 https://github.com/bitcoin/bitcoin/tarball/v0.6.0 # .tar.gz 16 https://github.com/bitcoin/bitcoin/zipball/v0.6.0 # .zip 17 18 For Ubuntu users, there is a ppa maintained by Matt Corallo which 19 you can add to your system so that it will automatically keep 20 bitcoin up-to-date. Just type 21 sudo apt-add-repository ppa:bitcoin/bitcoin 22 in your terminal, then install the bitcoin-qt package. 23 24 25 KNOWN ISSUES 26 27 Shutting down while synchronizing with the network 28 (downloading the blockchain) can take more than a minute, 29 because database writes are queued to speed up download 30 time. 31 32 33 NEW FEATURES SINCE BITCOIN VERSION 0.5 34 35 Initial network synchronization should be much faster 36 (one or two hours on a typical machine instead of ten or more 37 hours). 38 39 Backup Wallet menu option. 40 41 Bitcoin-Qt can display and save QR codes for sending 42 and receiving addresses. 43 44 New context menu on addresses to copy/edit/delete them. 45 46 New Sign Message dialog that allows you to prove that you 47 own a bitcoin address by creating a digital 48 signature. 49 50 New wallets created with this version will 51 use 33-byte 'compressed' public keys instead of 52 65-byte public keys, resulting in smaller 53 transactions and less traffic on the bitcoin 54 network. The shorter keys are already supported 55 by the network but wallet.dat files containing 56 short keys are not compatible with earlier 57 versions of Bitcoin-Qt/bitcoind. 58 59 New command-line argument -blocknotify=<command> 60 that will spawn a shell process to run <command> 61 when a new block is accepted. 62 63 New command-line argument -splash=0 to disable 64 Bitcoin-Qt's initial splash screen 65 66 validateaddress JSON-RPC api command output includes 67 two new fields for addresses in the wallet: 68 pubkey : hexadecimal public key 69 iscompressed : true if pubkey is a short 33-byte key 70 71 New JSON-RPC api commands for dumping/importing 72 private keys from the wallet (dumprivkey, importprivkey). 73 74 New JSON-RPC api command for getting information about 75 blocks (getblock, getblockhash). 76 77 New JSON-RPC api command (getmininginfo) for getting 78 extra information related to mining. The getinfo 79 JSON-RPC command no longer includes mining-related 80 information (generate/genproclimit/hashespersec). 81 82 83 84 NOTABLE CHANGES 85 86 BIP30 implemented (security fix for an attack involving 87 duplicate "coinbase transactions"). 88 89 The -nolisten, -noupnp and -nodnsseed command-line 90 options were renamed to -listen, -upnp and -dnsseed, 91 with a default value of 1. The old names are still 92 supported for compatibility (so specifying -nolisten 93 is automatically interpreted as -listen=0; every 94 boolean argument can now be specified as either 95 -foo or -nofoo). 96 97 The -noirc command-line options was renamed to 98 -irc, with a default value of 0. Run -irc=1 to 99 get the old behavior. 100 101 Three fill-up-available-memory denial-of-service 102 attacks were fixed. 103 104 105 NOT YET IMPLEMENTED FEATURES 106 107 Support for clicking on bitcoin: URIs and 108 opening/launching Bitcoin-Qt is available only on Linux, 109 and only if you configure your desktop to launch 110 Bitcoin-Qt. All platforms support dragging and dropping 111 bitcoin: URIs onto the Bitcoin-Qt window to start 112 payment. 113 114 115 PRELIMINARY SUPPORT FOR MULTISIGNATURE TRANSACTIONS 116 117 This release has preliminary support for multisignature 118 transactions-- transactions that require authorization 119 from more than one person or device before they 120 will be accepted by the bitcoin network. 121 122 Prior to this release, multisignature transactions 123 were considered 'non-standard' and were ignored; 124 with this release multisignature transactions are 125 considered standard and will start to be relayed 126 and accepted into blocks. 127 128 It is expected that future releases of Bitcoin-Qt 129 will support the creation of multisignature transactions, 130 once enough of the network has upgraded so relaying 131 and validating them is robust. 132 133 For this release, creation and testing of multisignature 134 transactions is limited to the bitcoin test network using 135 the "addmultisigaddress" JSON-RPC api call. 136 137 Short multisignature address support is included in this 138 release, as specified in BIP 13 and BIP 16.