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.
fanquake e5a680dc6a
[Doc] Update OS X build notes for 10.11 SDK
5 years ago
.tx qt: translation update prior to opening 0.12 translations 6 years ago
build-aux/m4 Only pass -lQt5PlatformSupport if >=Qt5.6 5 years ago
contrib Use runtime linking of QT libdbus, use custom/temp. SDK URL 5 years ago
depends Use runtime linking of QT libdbus, use custom/temp. SDK URL 5 years ago
doc [Doc] Update OS X build notes for 10.11 SDK 5 years ago
qa Merge #8066: [qa] test_framework: Use different rpc_auth_pair for each node 5 years ago
share build: Get rid of `CLIENT_DATE` 5 years ago
src Merge #7687: Stop treating importaddress'ed scripts as change 5 years ago
.gitattributes Separate protocol versioning from clientversion 7 years ago
.gitignore [trivial] Ignore 5 years ago
.travis.yml Use runtime linking of QT libdbus, use custom/temp. SDK URL 5 years ago [doc] Add basic git squash example 5 years ago
COPYING Update license year range to 2016 5 years ago
INSTALL Prettify some /Contrib READMEs 8 years ago build: add temporary fix for "bad magic number" error in out-of-tree builds 5 years ago readme: Omit phrasing; 'new' 5 years ago warn about needing autoconf if autoreconf is not found 5 years ago build: add armhf/aarch64 gitian builds 5 years ago Unify package name to as few places as possible without major changes 6 years ago

Bitcoin Core integration/staging tree

Build Status

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 useable, 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 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 (if the test dependencies are installed) with: qa/pull-tester/

The Travis CI system makes sure that every pull request is built for Windows, Linux, and OS X, 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.