fccd32efe6
22701a43464ab27ea83c8b49e2732ee647909a10 doc: update manual pages for 27.1rc1 (fanquake) 9e919072bd76b0c2048ef9df6ba7171e8be0ccf4 build: bump version to 27.1rc1 (fanquake) 9b4640c4bea984ebd496a4d6eb014fab7b6827fc doc: update release-notes.md for 27.1 (fanquake) 80032d691702f1e5eccb27571066bfc9b2415742 qt: 27.1rc1 translations update (Hennadii Stepanov) 423bd6dc68df1b023a699cb29825b946387a7b37 windeploy: Renew certificate (Ava Chow) 77b2321ca03dcbd5f77060510dc8a19e7f4fdfa2 depends: Fetch miniupnpc sources from an alternative website (Hennadii Stepanov) 31adcfa171c834a63237b4885ae19674fdff16f9 test: add GetAddedNodeInfo() CJDNS regression unit test (Jon Atack) 9cdb9edfb8d1a4b0c1ba39cea0d5cee2e28e1d31 p2p, bugfix: detect addnode cjdns peers in GetAddedNodeInfo() (Jon Atack) 3c26058da223b873094b62c30f2463ab0e629b6a crypto: disable asan for sha256_sse4 with clang and -O0 (Cory Fields) 0ba11cf90869fb437f6dce0c9430be4f899c0ea1 rpc: move UniValue in blockToJSON (willcl-ark) dedf319b08d5b76dc1752d8bc4e14d38dc54e100 gui: don't permit port in proxy IP option (willcl-ark) d1289a13006f43afa812f7ee8956f3d59449cfd0 gui: fix create unsigned transaction fee bump (furszy) Pull request description: Backports: * https://github.com/bitcoin-core/gui/pull/812 * https://github.com/bitcoin-core/gui/pull/813 * https://github.com/bitcoin/bitcoin/pull/30085 * https://github.com/bitcoin/bitcoin/pull/30094 * https://github.com/bitcoin/bitcoin/pull/30097 * https://github.com/bitcoin/bitcoin/pull/30149 * https://github.com/bitcoin/bitcoin/pull/30151 Bump to 27.1rc1. ACKs for top commit: stickies-v: re-ACK 22701a43464ab27ea83c8b49e2732ee647909a10 willcl-ark: reACK 22701a43464ab27ea83c8b49e2732ee647909a10 hebasto: re-ACK 22701a43464ab27ea83c8b49e2732ee647909a10. Tree-SHA512: 6eca44ba7e6664eb4677646597dfdaf56a241c8c3e95e0ab8929ee2fc3671303fc6c2634d359b4523dbd452ac5e54fd1f4c7c2bf7e9c5209395f8cb3b4753fb3
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.