Bitcoin Core integration/staging tree
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
fanquake 160d23677a
Merge bitcoin/bitcoin#28851: build: Patch Qt to handle minimum macOS version properly
2 days ago
.github Revert "ci: Avoid toolset ambiguity that MSVC can't handle" 1 week ago
.tx qt: Bump Transifex slug for 26.x 3 months ago
build-aux/m4 doc: update docs for CHECK_ATOMIC macro 1 month ago
build_msvc msvc: Specify `boost-date-time` package explicitly 1 week ago
ci ci: remove libz-dev from macOS build deps 3 days ago
contrib Merge bitcoin/bitcoin#28965: guix: remove input labels 3 days ago
depends Merge bitcoin/bitcoin#28851: build: Patch Qt to handle minimum macOS version properly 2 days ago
doc doc: remove mingw-w64 install for "older" systems 2 weeks ago
share depends: Bump MacOS minimum runtime requirement to 11.0 5 months ago
src Merge bitcoin/bitcoin#28368: Fee Estimator updates from Validation Interface/CScheduler thread 2 days ago
test Merge bitcoin/bitcoin#28784: rpc: keep `.cookie` file if it was not generated 2 days ago
.cirrus.yml Merge bitcoin/bitcoin#28076: util: Replace std::filesystem with util/fs.h 3 weeks ago
.editorconfig ci: Drop AppVeyor CI integration 2 years ago
.gitattributes Separate protocol versioning from clientversion 9 years ago
.gitignore build: produce a .zip for macOS distribution 3 months ago
.python-version Bump .python-version from 3.9.17 to 3.9.18 1 month ago
.style.yapf Update .style.yapf 6 months ago doc: Explain squashing with merge commits 2 years ago
COPYING doc: Update license year range to 2023 11 months ago doc: Added hyperlink for doc/build 2 years ago Merge bitcoin/bitcoin#28771: tests: Fix LCOV_OPTS to be in the correct position 2 weeks ago doc: Explain Bitcoin Core in 2 years ago doc: Add my key to 1 year ago build: make sure we can overwrite config.{guess,sub} 6 months ago Merge bitcoin/bitcoin#28919: build: Fix regression in "ARMv8 CRC32 intrinsics" test 2 weeks ago build: remove libcrypto as internal dependency in libbitcoinconsensus.pc 4 years ago

Bitcoin Core integration/staging tree

For an immediately usable, binary version of the Bitcoin Core software, see

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.


Bitcoin Core is released under the terms of the MIT license. See COPYING for more information or see

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 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 and useful hints for developers can be found in doc/


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/

There are also regression and integration tests, written in Python. These tests can be run (if the test dependencies are installed) with: test/functional/

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.


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.