# Gavin Andresen
# 2012-02-09 01:35:41
# https://bitcointalk.org/index.php?topic=63165.msg738756#msg738756

Re-posted from the bitcoin-development mailing list: @p{par}

 @p{brk}
I'd like version 0.6 to get lots of review, "soak time" and testing, so @p{brk}
please download and run release candidate 1 from: @p{brk}
 @s{(link)} @p{par}

You can review the code changes using github's compare feature: @p{brk}
 @s{(link)} @p{par}

Please report bugs using the github issue tracker. @p{par}

 @p{brk}
Release notes: @p{par}

NEW FEATURES SINCE BITCOIN VERSION 0.5 @p{brk}
@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{--} @p{brk}
Bitcoin-Qt can display and save QR codes for sending @p{brk}
and receiving addresses. @p{par}

New context menu on addresses to copy/edit/delete them. @p{par}

New Sign Message dialog that allows you to prove that you @p{brk}
own a bitcoin address by creating a digital @p{brk}
signature. @p{par}

Wallets created with this version of bitcoin will @p{brk}
use 33-byte 'compressed' public keys instead of @p{brk}
65-byte public keys, resulting in smaller @p{brk}
transactions and less traffic on the bitcoin @p{brk}
network. The shorter keys are completely @p{brk}
compatible with older versions. @p{par}

New command-line argument -blocknotify=@p{lt}command@s{gt} @p{brk}
that will spawn a shell process to run @p{lt}command@s{gt} @p{brk}
when a new block is accepted. @p{par}

validateaddress JSON-RPC api command output includes @p{brk}
two new fields for addresses in the wallet: @p{brk}
 pubkey : hexadecimal public key @p{brk}
 iscompressed : true if pubkey is a short 33-byte key @p{par}

New JSON-RPC api commands for dumping/importing @p{brk}
private keys from the wallet (dumprivkey, importprivkey). @p{par}

New JSON-RPC api command for getting information about @p{brk}
blocks (getblock, getblockhash). @p{par}

New JSON-RPC api command for getting extra information @p{brk}
related to mining (getmininginfo). @p{par}

 @p{brk}
NOTABLE CHANGES @p{brk}
@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-} @p{par}

The -nolisten, -noupnp and -nodnsseed command-line @p{brk}
options were renamed to -listen, -upnp and -dnsseed, @p{brk}
with a default value of 1. The old names are still @p{brk}
supported for compatibility (so specifying -nolisten @p{brk}
is automatically interpreted as -listen=0; every @p{brk}
boolean argument can now be specified as either @p{brk}
-foo or -nofoo). @p{par}

The -noirc command-line options was renamed to @p{brk}
-irc, with a default value of 0. Run -irc=1 to @p{brk}
get the old behavior. @p{par}

 @p{brk}
PRELIMINARY SUPPORT FOR MULTISIGNATURE TRANSACTIONS @p{brk}
@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-}@p{@p{--}-} @p{par}

This release has preliminary support for multisignature @p{brk}
transactions@p{--} transactions that require authorization @p{brk}
from more than one person or device before they @p{brk}
will be accepted by the bitcoin network. @p{par}

Prior to this release, multisignature transactions @p{brk}
were considered 'non-standard' and were ignored; @p{brk}
with this release multisignature transactions are @p{brk}
considered standard and will start to be relayed @p{brk}
and accepted into blocks. @p{par}

It is expected that future releases of Bitcoin-Qt @p{brk}
will support the creation of multisignature transactions, @p{brk}
once enough of the network has upgraded so relaying @p{brk}
and validating them is robust. @p{par}

For this release, creation and testing of multisignature @p{brk}
transactions is limited to the bitcoin test network using @p{brk}
the "addmultisigaddress" JSON-RPC api call. @p{par}

Short multisignature address support is included in this @p{brk}
release, as specified in BIP 16. Run with -bip16=0 to @p{brk}
turn off support for BIP 16. @p{brk}