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.
Janus Troelsen 58f1e54cbf Release Notes: Fix SHA256-with-SSE4 PR link hace 4 años
.github Mention reporting security issues responsibly hace 5 años
.tx qt: Set transifex slug to 0.14 hace 4 años
build-aux/m4 Explicitly search for bdb5.3. hace 4 años
contrib gitian: quick hack to fix version string in releases hace 4 años
depends Merge #10851: depends: fix fontconfig with newer glibc hace 4 años
doc Release Notes: Fix SHA256-with-SSE4 PR link hace 4 años
share Slightly overhaul NSI pixmaps hace 4 años
src qt: Translation update pre-rc3 hace 4 años
test Merge #11022: Basic keypool topup hace 4 años
.gitattributes Separate protocol versioning from clientversion hace 7 años
.gitignore Use shared config file for functional and util tests hace 4 años
.travis.yml Merge #10508: Run Qt wallet tests on travis hace 4 años Capitalize bullet points in CONTRIBUTING guide hace 4 años
COPYING [Trivial] Update license year range to 2017 hace 4 años Update INSTALL landing redirection notice for build instructions. hace 5 años Filter subtrees and and benchmarks from coverage report hace 4 años Rename test/pull-tester/ to test/functional/ hace 4 años Add MIT license to and share/ hace 5 años disable jni in builds hace 4 años Unify package name to as few places as possible without major changes hace 5 años

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.