We are pleased to announce the release of Bitcoin Core 0. The keypool bitcoin also contains several other improvements and bug fixes as described below. The following sections describe the most significant changes in this release. For full details, please see the Release Notes.
0 introduces full support for segwit in the wallet and user interfaces. A new address_type parameter has been added to the getnewaddress and addmultisigaddress RPCs to specify which type of address to generate. RPCs explicitly get their redeemscripts added to the wallet file. This means that downgrading after creating a segwit address will work, as long as the wallet file is up to date. All segwit keys in the wallet get an implicit redeemscript added, without it being written to the file. This means recovery of an old backup will work, as long as you use new software. All keypool keys that are seen used in transactions explicitly get their redeemscripts added to the wallet files.
Note that some RPCs do not yet support segwit addresses. Support for segwit in those RPCs will continue to be added in future versions. P2WPKH change outputs are now used by default if any destination in the transaction is a P2WPKH or P2WSH output. This is done to ensure the change output is as indistinguishable from the other outputs as possible in either case.
A checkbox has been added to the GUI to select whether a Bech32 address or P2SH-wrapped address should be generated when using segwit addresses. 32 it is checked by default. HD-wallets by default Due to a backward-incompatible change in the wallet database, wallets created with version 0. 0 will be rejected by previous versions. Replace-By-Fee by default in GUI The send screen now uses BIP125 RBF by default, regardless of -walletrbf. There is a checkbox to mark the transaction as final. 1 or use the replaceable argument for individual transactions.