589b56192f
a0d1f69b55doc: update release notes for 29.x (fanquake)6c0f26d3bdtest: check that creating a wallet does not log version info (Ava Chow)e685b4eca2test: Check that the correct versions are logged on wallet load (Ava Chow)25aa15ee7fwalletdb: Log the wallet version after it has been read from disk (Ava Chow)cf034172bftest: fix another intermittent failure in wallet_basic.py (Martin Zumsande)c966158426test: Fix intermittent failure in wallet_basic.py (Martin Zumsande)6c4e3de2actest: Use uninvolved pruned node in feature_pruning undo test (enoch)edd4073d70test: Fix nTimes typo in feature_pruning test (enoch)cc2fcdfc5ecmake: Allow `WITH_DBUS` on all Unix-like systems (Hennadii Stepanov)caec3cc41bcrypto: disable ASan for sha256_sse4 with Clang (fanquake)fabf4ff237tracing: fix invalid argument in mempool_monitor (William Casarin)f9d2c67a0ccmake: Respect user-provided configuration-specific flags (Hennadii Stepanov)6ed087dededoc: Fix test_bitcoin path (monlovesmango)2f6c802b54doc: Fix fuzz test_runner.py path (monlovesmango)f4d9546425qt: Replace stray tfm::format to cerr with qWarning (laanwj)5aa4956cd3gui: crash fix, disconnect numBlocksChanged() signal during shutdown (furszy)3665310808scripted-diff: Use bpf_cflags (MarcoFalke)4ed5c34abbtest: Add imports for util bpf_cflags (MarcoFalke)3dbd2b3d17refactor: Remove spurious virtual from final ~CZMQNotificationInterface (MarcoFalke)64552c83b2ci: Add workaround for vcpkg's libevent package (Hennadii Stepanov)85f3e1de68test: Handle empty string returned by CLI as None in RPC tests (Brandon Odiwuor)ca70d5cb25Remove support for RNDR/RNDRRS for aarch64 on Linux (laanwj) Pull request description: Backports for `29.x`: - #32184 - #32187 - #32248 - #32286 - #32312 - #32336 - #32353 - #32356 - #32389 - #32437 - #32454 - #32469 - #32483 - #32553 - https://github.com/bitcoin-core/gui/pull/864 - https://github.com/bitcoin-core/gui/pull/868 ACKs for top commit: willcl-ark: crACKa0d1f69b55Tree-SHA512: 72aafd17348aa4b602661efd07d48c6af6637c7349e7b032a65f46364e50094723d1c80dced71f0d5ddec59d6dafb72f0463944413a4d810a35cdca6b8272780
Bitcoin Core integration/staging tree
For an immediately usable, binary version of the Bitcoin Core software, see https://bitcoincore.org/en/download/.
What is Bitcoin Core?
Bitcoin Core connects to the Bitcoin peer-to-peer network to download and fully validate blocks and transactions. It also includes a wallet and graphical user interface, which can be optionally built.
Further information about Bitcoin Core is available in the doc folder.
License
Bitcoin Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.
Development Process
The master branch is regularly built (see doc/build-*.md for instructions) and tested, but it is not guaranteed to be
completely stable. Tags are created
regularly from release branches to indicate new official, stable release versions of Bitcoin Core.
The https://github.com/bitcoin-core/gui repository is used exclusively for the development of the GUI. Its master branch is identical in all monotree repositories. Release branches and tags do not exist, so please do not fork that repository unless it is for development reasons.
The contribution workflow is described in CONTRIBUTING.md and useful hints for developers can be found in doc/developer-notes.md.
Testing
Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.
Automated Testing
Developers are strongly encouraged to write unit tests for new code, and to
submit new unit tests for old code. Unit tests can be compiled and run
(assuming they weren't disabled during the generation of the build system) with: ctest. Further details on running
and extending unit tests can be found in /src/test/README.md.
There are also regression and integration tests, written
in Python.
These tests can be run (if the test dependencies are installed) with: build/test/functional/test_runner.py
(assuming build is your build directory).
The CI (Continuous Integration) systems make sure that every pull request is built for Windows, Linux, and macOS, and that unit/sanity tests are run automatically.
Manual Quality Assurance (QA) Testing
Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.
Translations
Changes to translations as well as new translations can be submitted to Bitcoin Core's Transifex page.
Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.
Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.