diff --git a/CMakeLists.txt b/CMakeLists.txt --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -7,7 +7,7 @@ ) project(bitcoin-abc - VERSION 0.22.5 + VERSION 0.22.6 DESCRIPTION "Bitcoin ABC is a full node implementation of the Bitcoin Cash protocol." HOMEPAGE_URL "https://www.bitcoinabc.org" ) diff --git a/contrib/aur/bitcoin-abc-qt/PKGBUILD b/contrib/aur/bitcoin-abc-qt/PKGBUILD --- a/contrib/aur/bitcoin-abc-qt/PKGBUILD +++ b/contrib/aur/bitcoin-abc-qt/PKGBUILD @@ -1,7 +1,7 @@ # Maintainer: Josh Ellithorpe pkgname=bitcoin-abc-qt -pkgver=0.22.5 +pkgver=0.22.6 pkgrel=0 pkgdesc="Bitcoin ABC with bitcoind, bitcoin-cli, bitcoin-tx, bitcoin-seeder and bitcoin-qt" arch=('i686' 'x86_64') diff --git a/contrib/aur/bitcoin-abc/PKGBUILD b/contrib/aur/bitcoin-abc/PKGBUILD --- a/contrib/aur/bitcoin-abc/PKGBUILD +++ b/contrib/aur/bitcoin-abc/PKGBUILD @@ -1,7 +1,7 @@ # Maintainer: Josh Ellithorpe pkgname=bitcoin-abc -pkgver=0.22.5 +pkgver=0.22.6 pkgrel=0 pkgdesc="Bitcoin ABC with bitcoind, bitcoin-tx, bitcoin-seeder and bitcoin-cli" arch=('i686' 'x86_64') diff --git a/doc/release-notes.md b/doc/release-notes.md --- a/doc/release-notes.md +++ b/doc/release-notes.md @@ -1,72 +1,7 @@ -# Bitcoin ABC 0.22.5 Release Notes +# Bitcoin ABC 0.22.6 Release Notes -Bitcoin ABC version 0.22.5 is now available from: +Bitcoin ABC version 0.22.6 is now available from: - + This release includes the following features and fixes: -- The `-upgradewallet` command line flag has been replaced in favor of the `upgradewallet` RPC. -- Fixed a bug where minimizing to the taskbar would not work properly when the - `-min` option was set on `bitcoin-qt`. -- Minimum supported Qt version has been bumped to `5.9.5` -- Fixed a bug where concurrent calls to the `walletpassphrase` RPC could deadlock. -- Minor logging improvements. -- Improved performance of verifying elliptic curve signatures. - -Updated RPCs ------------- - -- The `getchaintxstats` RPC now returns the additional key of - `window_final_block_height`. -- The `getnetworkinfo` and `getpeerinfo` commands now contain - a new `servicesnames` field with decoded network service flags. -- `walletprocesspsbt` and `walletcreatefundedpsbt` now include BIP 32 - derivation paths by default for public keys if we know them. This can be - disabled by setting `bip32derivs` to `false`. - -Updated settings ----------------- - -- The `-debug=db` logging category, which was deprecated in 0.22.4 and replaced by - `-debug=walletdb` to distinguish it from `coindb`, has been removed. - -- Users setting custom `dbcache` values can increase their setting slightly - without using any more real memory. Recent changes reduced the memory use - by about 9% and made chainstate accounting more accurate (it was underestimating - the use of memory before). For example, if you set a value of "450" before, you - may now set a value of "500" to use about the same real amount of memory. (#16957) - -P2P and network changes ------------------------ - -#### Removal of reject network messages from Bitcoin ABC (BIP61) - -The command line option to enable BIP61 (`-enablebip61`) has been removed. - -This feature has been disabled by default since Bitcoin ABC version 0.21.9. -Nodes on the network can not generally be trusted to send valid ("reject") -messages, so this should only ever be used when connected to a trusted node. -Please use the recommended alternatives if you rely on this deprecated feature: - -* Testing or debugging of implementations of the Bitcoin P2P network protocol - should be done by inspecting the log messages that are produced by a recent - version of Bitcoin ABC. Bitcoin ABC logs debug messages - (`-debug=`) to a stream (`-printtoconsole`) or to a file - (`-debuglogfile=`). - -* Testing the validity of a block can be achieved by specific RPCs: - - `submitblock` - - `getblocktemplate` with `'mode'` set to `'proposal'` for blocks with - potentially invalid POW - -* Testing the validity of a transaction can be achieved by specific RPCs: - - `sendrawtransaction` - - `testmempoolaccept` - -* Wallets should not use the absence of "reject" messages to indicate a - transaction has propagated the network, nor should wallets use "reject" - messages to set transaction fees. Wallets should rather use fee estimation - to determine transaction fees and set replace-by-fee if desired. Thus, they - could wait until the transaction has confirmed (taking into account the fee - target they set (compare the RPC `estimatesmartfee`)) or listen for the - transaction announcement by other network peers to check for propagation. diff --git a/doc/release-notes.md b/doc/release-notes/release-notes-0.22.5.md copy from doc/release-notes.md copy to doc/release-notes/release-notes-0.22.5.md