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.
MacroFake ec0a4ad677
Merge bitcoin/bitcoin#25538: [0.21] test: replace hashlib.ripemd160 with an own implementation
3 months ago
.github doc: Remove label from good first issue template 2 years ago
.tx tx: Update transifex slug for 0.21 2 years ago
build-aux/m4 build: check if -lsocket is required with *ifaddrs 1 year ago
build_msvc build: Bump version to 0.21.2rc1 1 year ago
ci ci: Build with --enable-werror by default, and document exceptions 1 year ago
contrib Use latest signapple commit 1 year ago
depends depends: update Qt 5.9 source url 1 year ago
doc release: bump RC to 0 (-final) 1 year ago
share doc: add signet to share/examples/bitcoin.conf 2 years ago
src refactor: include a missing <limits> header in fs.cpp 4 months ago
test Swap out hashlib.ripemd160 for own implementation 3 months ago
.appveyor.yml Update vcpkg checkout commit. 2 years ago
.cirrus.yml ci: Run fuzzer task for the master branch only 1 year ago
.fuzzbuzz.yml ci: Add fuzzbuzz integration 2 years ago
.gitattributes Separate protocol versioning from clientversion 8 years ago
.gitignore .gitignore: ignore qa-assets/ folder 2 years ago
.python-version .python-version: Specify full version 3.5.6 4 years ago
.style.yapf test: .style.yapf: Set column_limit=160 4 years ago
.travis.yml ci: Run windows ci config on cirrus 2 years ago
CODEOWNERS doc: Add comments and additional reviewers to CODEOWNERS file 2 years ago Replace `hidden service` with `onion service` 2 years ago
COPYING doc: Update license year range to 2020 3 years ago Update INSTALL landing redirection notice for build instructions. 6 years ago build: use DIR_FUZZ_SEED_CORPUS if specified for cov_fuzz target 2 years ago doc: Mention repo split in the READMEs 2 years ago doc: Remove explicit mention of version from 3 years ago scripted-diff: Bump copyright of files changed in 2019 3 years ago build: Restrict check for CRC32C intrinsic to aarch64 4 months ago build: remove libcrypto as internal dependency in libbitcoinconsensus.pc 3 years ago

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, or read the original 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, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: test/functional/

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.


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.