0cbdc6b380
4f23c8636498f7e5adbe0264a0dc66a566c4b1b9 [WIP] doc: update release notes for 27.x (fanquake) 54bb9b0541d44972726a187e382a6b267942f47a test: add test for modififed walletprocesspsbt calls (willcl-ark) f22b9ca70c867a02d6f578dc56d4997b7a4ff9c9 wallet: fix FillPSBT errantly showing as complete (willcl-ark) 05192ba84c2d0ef727c9dbc1e6af4ce8a59458fa init: change shutdown order of load block thread and scheduler (Martin Zumsande) ab422066527992d53c92bb482c6b993f089b2999 Reapply "test: p2p: check that connecting to ourself leads to disconnect" (Sebastian Falbesoner) 064f2146735c88823f73f7531fc36d21d1ddb6f3 net: prevent sending messages in `NetEventsInterface::InitializeNode` (Sebastian Falbesoner) 0933cf53b48a160612873978f38ef4ff70e74847 net: fix race condition in self-connect detection (Sebastian Falbesoner) fa90989503494b77a0329390dc5e32d0c5e5c283 psbt: Check non witness utxo outpoint early (Ava Chow) Pull request description: Backports: * https://github.com/bitcoin/bitcoin/pull/29855 * https://github.com/bitcoin/bitcoin/pull/30357 * https://github.com/bitcoin/bitcoin/pull/30394 (modified test commit) * https://github.com/bitcoin/bitcoin/pull/30435 ACKs for top commit: stickies-v: ACK 4f23c8636498f7e5adbe0264a0dc66a566c4b1b9 willcl-ark: ACK 4f23c8636498f7e5adbe0264a0dc66a566c4b1b9 Tree-SHA512: 5c26445f0855f9d14890369ce19873b0686804eeb659e7d6da36a6f404f64d019436e1e6471579eaa60a96ebf8f64311883b4aef9d0ed528a95bd610c101c079
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 in configure) with: make check. 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: test/functional/test_runner.py
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.