Release Notes for Bitcoin Cash Node version 28.0.1
Bitcoin Cash Node version 28.0.1 is now available from:
Overview
This release of Bitcoin Cash Node (BCHN) is a patch release. It includes various corrections and improvements, most notably a performance improvement for large block processing, which should benefit non-mining and mining nodes alike.
Usage recommendations
Users who are running v28.0.0 or older are encouraged to upgrade to v28.0.1.
Network changes
None
Added functionality
None
Deprecated functionality
None
Modified functionality
- The peer-to-peer network's block propagation logic has been improved to allow for lower-latency block propagation.
In particular, block downloads now request the latest block from up to 3 peers simultaneously so that the node has a
better chance of receiving the latest block as quickly as possible. - The ABLA startup checks have been simplified and reduced to be simpler and faster. This should improve Bitcoin Cash
Node startup times (in particular if running on an HDD-based system). To enable the old more thorough ABLA checks at
app startup, start the node with the-check-abla
option.
Removed functionality
None
New RPC methods
None
User interface changes
- The
getpeerinfo
RPC returns two new boolean fields,bip152_hb_to
and
bip152_hb_from
, that respectively indicate whether we selected a peer to be
in compact blocks high-bandwidth mode or whether a peer selected us as a
compact blocks high-bandwidth peer. High-bandwidth peers send new block
announcements via acmpctblock
message rather than the usual inv/headers
announcements. See BIP 152 for more details. - The
getnetworkinfo
RPC method results now include two new keys:connections_in
andconnections_out
. These
correspond to the current number of active inbound and outbound peer-to-peer connections, respectively.
Regressions
Bitcoin Cash Node 28.0.1 does not introduce any known regressions as compared to 28.0.0.
Limitations
The following are limitations in this release of which users should be aware:
-
CashToken support is low-level at this stage. The wallet application does
not yet keep track of the user's tokens.
Tokens are only manageable via RPC commands currently.
They only persist through the UTXO database and block database at this
point.
There are existing RPC commands to list and filter for tokens in the UTXO set.
RPC raw transaction handling commands have been extended to allow creation
(and sending) of token transactions.
Interested users are advised to consult the functional test in
test/functional/bchn-rpc-tokens.py
for examples on token transaction
construction and listing.
Future releases will aim to extend the RPC API with more convenient
ways to create and spend tokens, as well as upgrading the wallet storage
and indexing subsystems to persistently store data about tokens of interest
to the user. Later we expect to add GUI wallet management of Cash Tokens. -
Transactions with SIGHASH_UTXO are not covered by DSProofs at present.
-
P2SH-32 is not used by default in the wallet (regular P2SH-20 remains
the default wherever P2SH is treated). -
The markup of Double Spend Proof events in the wallet does not survive
a restart of the wallet, as the information is not persisted to the
wallet. -
The ABLA algorithm for BCH is currently temporarily set to cap the max block
size at 2GB. This is due to limitations in the p2p protocol (as well as the
block data file format in BCHN).
Known Issues
Some issues could not be closed in time for release, but we are tracking all
of them on our GitLab repository.
-
The minimum macOS version is 10.14 (Mojave).
Earlier macOS versions are no longer supported. -
Windows users are recommended not to run multiple instances of bitcoin-qt
or bitcoind on the same machine if the wallet feature is enabled.
There is risk of data corruption if instances are configured to use the same
wallet folder. -
Some users have encountered unit tests failures when running in WSL
environments (e.g. WSL/Ubuntu). At this time, WSL is not considered a
supported environment for the software. This may change in future.
It has been reported that using WSL2 improves the issue. -
doc/dependencies.md
needs revision (Issue). -
For users running from sources built with BerkeleyDB releases newer than
the 5.3 which is used in this release, please take into consideration
the database format compatibility issues described in Issue.
When building from source it is recommended to use BerkeleyDB 5.3 as this
avoids wallet database incompatibility issues with the official release. -
The
test_bitcoin-qt
test executable fails on Linux Mint 20
(see Issue). This does not otherwise appear to impact the functioning
of the BCHN software on that platform. -
With a certain combination of build flags that included disabling
the QR code library, a build failure was observed where an erroneous
linking against the QR code library (not present) was attempted (Issue). -
Possible out-of-memory error when starting bitcoind with high excessiveblocksize
value (Issue) -
A problem was observed on scalenet where nodes would sometimes hang for
around 10 minutes, accepting RPC connections but not responding to them
(see Issue). -
Startup and shutdown time of nodes on scalenet can be long (see Issue).
-
Race condition in one of the
p2p_invalid_messages.py
tests (see Issue). -
Occasional failure in bchn-txbroadcastinterval.py (see Issue).
-
wallet_keypool.py test failure when run as part of suite on certain many-core
platforms (see Issue). -
Spurious 'insufficient funds' failure during p2p_stresstest.py benchmark
(see Issue). -
If compiling from source, secp256k1 now no longer works with latest openssl3.x series.
There are workarounds (see Issue). -
Spurious
AssertionError: Mempool sync timed out
in several tests
(see Issue). -
For some platforms, there may be a need to install additional libraries
in order to build from source (see Issue and discussion in MR 1523). -
More TorV3 static seeds may be needed to get
-onlynet=onion
working
(see Issue). -
Memory usage can be very high if repeatedly doing RPC
getblock
with
verbose=2 on a hash of known big blocks (see Issue). -
A GUI crash failure was observed when attempting to encrypt a large imported
wallet (see Issue). -
The 'wallet_multiwallet' functional test fails on latest Arch Linux due to
a change in semantics in a dependency (see Issue). This is not expected to impact functionality otherwise, only a particular edge case
of the test. -
The 'p2p_extversion' functional test is sensitive to timing issues when
run at high load (see Issue).
Changes since Bitcoin Cash Node 28.0.0
New documents
None
Removed documents
None
Notable commits grouped by functionality
Security or consensus relevant fixes
- 5ac8002 net: Fix potential for UB in
CNode::ReceiveMsgBytes
- 2b92f73 mempool: Fix potential for bug in mempool removeForBlock()
Interfaces / RPC
- 2aaadb6 net, rpc: expose high bandwidth mode state via getpeerinfo
Features in internal development: support for UTXO commitments
None
Data directory changes
None
Performance optimizations
- 6961e64 net: Avoid excess CPU usage by
msghand
thread; fix "early wake up" logic - fa0d374 Improve
DisconnectedBlockTransactions::addForBlock
performance - ecd1392 ABLA: Improve performance of app init, turn off slower checks by default
- ac22ffd [net] Parallel compact block downloads
GUI
None
Code quality
- 70b94b0 [net processing] Tidy up sendcmpct processing
Documentation updates
- 4a8036c Update Ubuntu and Debian build guide
Build / general
None
Build / Linux
None
Build / Windows
None
Build / MacOSX
None
Tests / test framework
- ae96a7f Improvements to test bchn-txbroadcastinterval.py
- 3e6cff5 [tests] Allow outbound connections in functional tests.
- c2f4061 util: Add CHECK_NONFATAL and use it in src/rpc
- 1d5a02e Added partial backport of core header/cpp file "util/check.*"
- 124e41b Add tests for parallel compact block downloads
Benchmarks
None
Seeds / seeder software
None
Maintainer tools
None
Infrastructure
None
Cleanup
- b18fb57 [qa] Bump version to 28.0.1, rotate release notes
- a69c5c6 net: Remove extraneous/bad log line from net_processing.cpp
- e887c38 Update DisconnectedBlockTransactions::addForBlock to use CHECK_NONFATAL rather than assert()
Continuous Integration (GitLab CI)
None
Compatibility
None
Backports
- 3e6cff5 [tests] Allow outbound connections in functional tests.
- c2f4061 util: Add CHECK_NONFATAL and use it in src/rpc
- 1d5a02e Added partial backport of core header/cpp file "util/check.*"
- 2aaadb6 net, rpc: expose high bandwidth mode state via getpeerinfo
- 70b94b0 [net processing] Tidy up sendcmpct processing
- ac22ffd [net] Parallel compact block downloads
- 124e41b Add tests for parallel compact block downloads