Posted On 03.07.1953
26 February 2018 Bitcoin Core version 0. Getaccountaddress bitcoin is a new major version release, including new features, various bugfixes and performance improvements, as well as updated translations.
How to Upgrade If you are running an older version, shut it down. The first time you run version 0. 0 or newer, your chainstate database will be converted to a new format, which will take anywhere from a few minutes to half an hour, depending on the speed of your machine. Note that the block database format also changed in version 0. 0 and there is no automatic upgrade code from before version 0.
However, as usual, old wallet versions are still supported. Downgrading warning Wallets created in 0. 16 and later are not compatible with versions prior to 0. 16 and will not work if you try to use newly created wallets in older versions. Existing wallets that were created with older versions are not affected by this. Compatibility Bitcoin Core is extensively tested on multiple operating systems using the Linux kernel, macOS 10. Bitcoin Core should also work on most other Unix-like systems but is not frequently tested on them.
Notable changes Wallet changes Segwit Wallet Bitcoin Core 0. 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.