e55c49f851
f541b92cf2bb7f8f708f147bd320becf48587d14 depends: expat 2.7.3 (fanquake) 2ebf4356e63def5b306c1061a2d4e9d6d0c782e9 depends: libxcb 1.17.0 (Hennadii Stepanov) ba7ac870a32ad699a2b5b86a9b51506b75238ab2 depends: xcb_proto 1.17.0 (Hennadii Stepanov) 42d0692f9131d15cd41d98378ad2c2616bfe786f depends: libxcb-util-cursor 0.1.6 (fanquake) 25b85919ab62fb8c90bb2c51c76c9a5c036199af depends: libxcb 1.15 (fanquake) d129384ca97fb2f9c0185d3d47391b9ec3ed71cf depends: libxcb-util-wm 0.4.2 (fanquake) 0b857ae9e55512a4416bddedaa763fd0957c3d4c depends: libxcb-util-renderutil 0.3.10 (fanquake) 35e50488b25ad1478fd91ce297fd0918eb1e82d0 depends: libxcb-util-keysyms 0.4.1 (fanquake) 74b68ad28ba28642ed96da93c89a25efa329f6bc depends: libxcb-util-image 0.4.1 (fanquake) 5bc0dde85d74892b64b655a4476ad22ed5509b1a depends: libxcb-util 0.4.1 (fanquake) 8d07292c286fd737a9f89d449eee5657a9b8b032 depends: libXau 1.0.12 (fanquake) Pull request description: Update libxcb and related package versions: libXau 1.0.9 -> 1.0.12 libxcb 1.14 -> 1.17 libxcb_util 0.4.0 -> 0.4.1 libxcb_util_cursor 0.1.5 -> 0.1.6 libxcb_util_image 0.4.0 -> 0.4.1 libxcb_util_keysyms 0.4.0 -> 0.4.1 libxcb_util_render 0.3.9 -> 0.3.10 libxcb_util_wm 0.4.1 -> 0.4.2 xcb_proto 1.15.2 -> 1.17.0 These recently became static in #33537. Also update expat 2.4.8 -> 2.7.3. ACKs for top commit: hebasto: ACK f541b92cf2bb7f8f708f147bd320becf48587d14, due to the last commit, I also tested an LTO build on Ubuntu 25.10 using GCC 15.2.0. Tree-SHA512: 63f32e22743d8fa59b6e78fa8ea301e5cfaa55832454a8bc87ebb18e3d03379e9354519acd040ce861b4b1f3879b9cf9fb724dca69f6e0f8d2ef9ebfa7a032bf
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/license/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 tested on Windows, Linux, and macOS. The CI must pass on all commits before merge to avoid unrelated CI failures on new pull requests.
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.