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.
Pieter Wuille eece63fa72 Switch blocks to a constant-space Merkle root/branch algorithm. 5 lat temu
.tx qt: translation update prior to opening 0.12 translations 5 lat temu
build-aux/m4 build: Use fPIC rather than fPIE for qt objects. 5 lat temu
contrib Merge pull request #7042 5 lat temu
depends Merge pull request #7059 5 lat temu
doc Connect to Tor hidden services by default 5 lat temu
qa Merge pull request #6871 5 lat temu
share [trivial] Remove obsolete share/qt/ 5 lat temu
src Switch blocks to a constant-space Merkle root/branch algorithm. 5 lat temu
.gitattributes Separate protocol versioning from clientversion 6 lat temu
.gitignore Merge pull request #6813 5 lat temu
.travis.yml Add basic coverage reporting for RPC tests 5 lat temu Add PR title prefix for trivial changes [skip ci] 5 lat temu
COPYING Update contrib/debian/copyright 5 lat temu
INSTALL Prettify some /Contrib READMEs 7 lat temu build: Set osx permissions in the dmg to make Gatekeeper happy 5 lat temu [qa] Extend 5 lat temu Bugfix: Replace bashisms with standard sh to fix build on non-BASH systems 6 lat temu Update key.cpp to new secp256k1 API 5 lat temu libbitcoinconsensus: Add pkg-config support 6 lat temu

Bitcoin Core integration/staging tree

Build Status

What is Bitcoin?

Bitcoin is an experimental new 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 useable, binary version of the Bitcoin Core software, see


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 and tested, but is not guaranteed to be completely stable. Tags are created regularly to indicate new official, stable release versions of Bitcoin Core.

The contribution workflow is described in

The developer mailing list should be used to discuss complicated or controversial changes before working on a patch set.

Developer IRC can be found on Freenode at #bitcoin-core-dev.


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

There are also regression and integration tests of the RPC interface, written in Python, that are run automatically on the build server. These tests can be run with: qa/pull-tester/

The Travis CI system makes sure that every pull request is built for Windows and Linux, OSX, and that unit and sanity tests are automatically run.

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.