Bitcoin Core integration/staging tree
Clone or download
MarcoFalke Merge #15185: docs: Spelling error fix on
31097b7 docs: Spelling error fix on (benthecarman)

Pull request description:

Tree-SHA512: f4deb837d0d221c5ff118bbf8cf44600a97099ea330341b94561ffa546c33a90a58bef8284b343df3bfa1376d2e80f2002ac8e393a092dbf699568b5df1e8611
Latest commit 003a47f Jan 17, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Get more info about GUI-related issue on Linux Dec 27, 2018
.travis If tests are ran with (ASan + LSan), Docker needs access to ptrace Dec 28, 2018
.tx tx: Update transifex slug 016x→017x Aug 2, 2018
build-aux/m4 Bump the minimum Qt version to 5.2 Nov 13, 2018
build_msvc Merge #14151: windows: Fix remaining compiler warnings (MSVC) Jan 16, 2019
contrib Merge #15165: contrib: Allow use of github API authentication in gith… Jan 16, 2019
depends Merge #13884: depends: Enable bdb unicode support for Windows Jan 3, 2019
doc docs: Spelling error fix on Jan 17, 2019
share Merge #14701: build: Add CLIENT_VERSION_BUILD to CFBundleGetInfoString Dec 12, 2018
src Merge #14250: qt: Remove redundant stopThread() and stopExecutor() si… Jan 17, 2019
test Merge #14409: utils and libraries: Make 'blocksdir' always net specific Jan 16, 2019
.appveyor.yml Fix remaining compiler warnings (MSVC). Move disabling of specific wa… Jan 15, 2019
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.gitignore gitignore contents of db4 folder Oct 19, 2018
.python-version [test] Travis: enforce Python 3.4 support in functional tests Dec 12, 2018
.travis.yml Merge #15020: Build: add names to Travis jobs Jan 3, 2019 (IRC logs) not available anymore Jan 1, 2019
COPYING [Trivial] Update license year range to 2019 Dec 31, 2018 Update INSTALL landing redirection notice for build instructions. Oct 5, 2016 build: Add bitcoin-tx.exe into Windows installer Nov 9, 2018 [doc] conf: Remove deprecated options from docs, Other cleanup Nov 7, 2018 Add "export LC_ALL=C" to all shell scripts Jun 14, 2018 configure: bitcoin-tx doesn't need libevent, so don't pull it in Jan 12, 2019 Unify package name to as few places as possible without major changes Dec 14, 2015

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 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.