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.
MarcoFalke d20d6ac545
Merge bitcoin/bitcoin#23672: tests: Add data-driven testcases to
6 hours ago
.github doc: Remove label from good first issue template 1 year ago
.tx qt: Bump transifex slug for 22.x 8 months ago
build-aux/m4 build: qt 5.15.2 3 days ago
build_msvc doc: Update `build_msvc/` for Qt 5.15.2 3 days ago
ci test: Bump shellcheck version to 0.8.0 6 days ago
contrib build: qt 5.15.2 3 days ago
depends build, qt: Fix regression in rendering on macOS Big Sur 3 days ago
doc build: freetype 2.11.0 3 days ago
share test: Enable SC2086 shellcheck rule 3 weeks ago
src Merge bitcoin-core/gui#493: qt: Handle Android back key in the Node window 2 days ago
test Merge bitcoin/bitcoin#23672: tests: Add data-driven testcases to 6 hours ago
.cirrus.yml ci: Bump Qt to 5.15.2 in the native Windows task 3 days ago
.editorconfig ci: Drop AppVeyor CI integration 3 months ago
.gitattributes Separate protocol versioning from clientversion 7 years ago
.gitignore build: add *~ to .gitignore 7 months ago
.python-version Bump minimum python version to 3.6 1 year ago
.style.yapf test: .style.yapf: Set column_limit=160 3 years ago Enable TLS in links in documentation 3 months ago
COPYING doc: Update license year range to 2021 11 months ago doc: Added hyperlink for doc/build 3 months ago Add minisketch dependency 2 months ago doc: Rework internal and external links 10 months ago
REVIEWERS release: remove gitian 3 months ago doc: Suggest `` as keyserver in 4 weeks ago scripted-diff: Bump copyright of files changed in 2019 2 years ago Merge bitcoin/bitcoin#23152: build: add `--enable-lto` configuration option 2 weeks ago build: remove libcrypto as internal dependency in libbitcoinconsensus.pc 2 years ago

Bitcoin Core integration/staging tree

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

Further information about Bitcoin Core is available in the doc folder.

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 read the original Bitcoin whitepaper.


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.