3761863e14
624c745e4917306198443fc9fb3465e1d6f8f214 doc: update release notes for v30.x (fanquake) 0f01a4c2458bb5a3d6584697345c116512e62ebf ci: Check windows manifests for all executables (Max Edwards) 4664621abeac2c2311d0d1aee878d844d5371ea5 ci: use a more generic way of finding mt.exe (Max Edwards) aa937589326dfc7d315fd19f83b7372df15d09ab ci: remove 3rd party js from windows dll gha job (Max Edwards) 290526bc6dec1cdf0f6db8415b05a794260de14a wallet: fix removeprunedfunds bug with conflicting transactions (Martin Zumsande) 4deda48fa44989ee73278fe4eb6e8a27e9e56807 build: Remove outdated comment about -ffile-prefix-map (MarcoFalke) eda6c979bd7b6971560938c1a4b24671894c6f44 doc: Remove outdated -fdebug-prefix-map section in dev notes (MarcoFalke) c294b661266bcf81b16894aa6bff0dafa88d7b86 build: Temporarily remove confusing and brittle -fdebug-prefix-map (MarcoFalke) 33195bdd9ee9ded5aec562602978fb89d2d99f4b test: allow overriding tar in get_previous_releases (fanquake) 810c75b9b1a7efb2f8c021fcdc278488f702cd98 chore: Update outdated GitHub Actions versions (Padraic Slattery) de79f7d01ce43189006cadf08296672fb4d5d5ca qa: Fix Windows logging bug (Hennadii Stepanov) 311da7fee3aba2e6765e193f963b568cf668dbd1 test: check wallet rescan properly in feature_pruning (brunoerg) 4431a60f9c75da2a417d50cd87bcd269f3147489 test: fix feature_pruning when built without wallet (brunoerg) 7e1090f5e8056dd6042ecfe34eae3992a81a18fd psbt: Fix `PSBTInputSignedAndVerified` bounds `assert` (Lőrinc) 22bd00651a48a50ec1d3b7f717b375f62719b456 doc: add 433 (Pay to Anchor) to bips.md (Sebastian Falbesoner) Pull request description: Backports: * #32513 * #34185 * #34272 * #34252 * #34281 * #34282 * #34344 * #34358 * #34390 * #34413 ACKs for top commit: willcl-ark: ACK 624c745e4917306198443fc9fb3465e1d6f8f214 marcofleon: ACK 624c745e4917306198443fc9fb3465e1d6f8f214 Tree-SHA512: 65f413419b50784d2661d89f2044acd5196eacd50841bb93d7437b83bd23ce535565168cd4c53f96ba485863a911f5a1ea5476b22955d6b931b65e87f78b9a17
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.