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.
John Newbery 4c14e7b67c
[wallet] Fix zapwallettxes/multiwallet interaction.
3 years ago
.github Make default issue text all comments to make issues more readable 4 years ago
.tx tx: Update transifex slug for 0.16 3 years ago
build-aux/m4 Merge #12294: [Docs] Create NetBSD build instructions and fix compilation 3 years ago
contrib Merge #12636: backport: #11995 Fix Qt build with Xcode 9 3 years ago
depends depends: Fix Qt build with XCode 9.3 3 years ago
doc List support for BIP173 in 3 years ago
share Avoid launching as admin when NSIS installer ends. 3 years ago
src [wallet] Fix zapwallettxes/multiwallet interaction. 3 years ago
test [qa] Handle disconnect_node race 3 years ago
.gitattributes Separate protocol versioning from clientversion 7 years ago
.gitignore [build] .gitignore: add QT Creator artifacts 4 years ago
.travis.yml travis: Don't fetch --unshallow when no longer shallow-cloning 3 years ago [docs] links to code style guides 4 years ago
COPYING [Trivial] Update license year range to 2018 3 years ago Update INSTALL landing redirection notice for build instructions. 5 years ago Merge #11842: [build] Add missing stuff to clean-local 4 years ago Rename test/pull-tester/ to test/functional/ 4 years ago Add MIT license to and share/ 5 years ago build: bump version to 0.16.0 3 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. 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 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.