a30fd40735
5a2d98c640doc: Remove outdated comment (Hennadii Stepanov)8426e3a8a1fuzz: Bump FuzzedDataProvider.h (MarcoFalke)14e3f2a1c9fuzz: Bump FuzzedDataProvider.h (MarcoFalke)a48c9d3161fuzz: Update FuzzedDataProvider.h from upstream (LLVM) (practicalswift)6746cd078bdoc: add signet to doc/bitcoin-conf.md (Jon Atack)58975d5c0adoc: add signet to share/examples/bitcoin.conf (Jon Atack)b35711efdeUpdate vcpkg checkout commit. (Aaron Clauson)3a12672419GUI: Write PSBTs to file with binary mode (Andrew Chow)36ecf5eb87tests: Test that a fully signed tx given to signrawtx is unchanged (Andrew Chow)4ef1e4bd40test: disallow sendtoaddress/sendmany when private keys disabled (Jon Atack)d6b5eb5fccDisallow sendtoaddress and sendmany when private keys disabled (Andrew Chow)08dada8456util: Disallow negative mocktime (MarcoFalke)95218ee95cnet: Avoid UBSan warning in ProcessMessage(...) (practicalswift)4607019798fix the unreachable code at feature_taproot (Bruno Garcia)6dc58e9945qt: Use "fusion" style on macOS Big Sur with old Qt (Hennadii Stepanov)e2ebc8567araise helpMessageDialog (randymcmillan)a98f211940Fix MSVC build after gui#176 (Hennadii Stepanov)bdc64c9030qt: Stop the effect of hidden widgets on the size of QStackedWidget (Hennadii Stepanov)7bc4498234qt: Fix TxViewDelegate layout (Hennadii Stepanov)b7086e69ffqt: Add TransactionOverviewWidget class (Hennadii Stepanov)0dba346a56qt: Use layout manager for Create Wallet dialog (Hennadii Stepanov)7bf3ed495bBugfix: GUI: Restore SendConfirmationDialog button default to "Yes" (Luke Dashjr)bdce029191test: add test for banning of non-IP addresses (Vasil Dimov)c33fbab25cnet: allow CSubNet of non-IP networks (Vasil Dimov) Pull request description: Current backports for *0.21.1*. One conflict was in the test case. ACKs for top commit: ajtowns: ACK5a2d98c640-- checked 'rebased-from' patches are in master, and rebased patches are clean rebases (except for the first one which changes `""s` to `std::string("")` to avoid c++17 dependency). commits seem fine, but haven't reviewed in detail. fanquake: ACK5a2d98c640- branched off `0.21` and redid the backports. Minor conflict inc33fbab25c. The diff between my branch and #20901 was just in release notes, `_CLIENT_VERSION_RC` (#20901 branched before95ea54ba08) and #21490 which has already been merged into `0.21`. Tree-SHA512: 75d16d3cf9066a45759758b8185dc3b9dad6a6102c2ac9921f758a310e48d5d3122f0dafa515df42475235fc66a42cc04dd156ee1e61c86a1238bd11707642ea
Bitcoin Core integration/staging tree
What is Bitcoin?
Bitcoin is an experimental digital currency that enables instant payments to anyone, anywhere in the world. Bitcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Bitcoin Core is the name of open source software which enables the use of this currency.
For more information, as well as an immediately usable, binary version of the Bitcoin Core software, see https://bitcoincore.org/en/download/, or read the original whitepaper.
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, that are run automatically on the build server.
These tests can be run (if the test dependencies are installed) with: test/functional/test_runner.py
The Travis CI system makes 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.
Translators should also subscribe to the mailing list.