Skip to content
Bitcoin integration/staging tree
Branch: 0.11.x-ljrP
Clone or download
Pull request Compare This branch is 410 commits ahead, 11953 commits behind bitcoin:master.
Type Name Latest commit message Commit time
Failed to load latest commit information.
.tx Change transifex slug to `translation-011x` May 1, 2015
build-aux/m4 Merge branch 'backports-for-0.11.3' into 0.11.x-ljrF Nov 18, 2015
contrib Merge branch '0.11.x-ljrF' (zeromq part) into 0.11.x-ljrF Nov 18, 2015
depends Merge branch '0.11.x-ljrF' (zeromq part) into 0.11.x-ljrF Nov 18, 2015
doc Merge branch 'dcmp-0.11.x' into 0.11.x-ljrP Nov 18, 2015
qa Merge branch '0.11.x-ljrF' (zeromq part) into 0.11.x-ljrF Nov 18, 2015
share Hardcoded seeds update June 2015 Jun 25, 2015
src Merge branch 'dcmp-0.11.x' into 0.11.x-ljrP Nov 18, 2015
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.gitignore Add libbitcoinconsensus.pc to .gitignore Dec 20, 2014
.travis.yml travis: for travis generating an extra build Sep 22, 2015
COPYING [Trivial] Update COPYING May 14, 2015
INSTALL Prettify some /Contrib READMEs Oct 22, 2013 Add to source tarball. Sep 22, 2015 doc: update mailing list address Jun 22, 2015 Bugfix: Replace bashisms with standard sh to fix build on non-BASH sy… Oct 3, 2014 Merge branch '0.11.x-ljrF' (zeromq part) into 0.11.x-ljrF Nov 18, 2015

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

Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.

If it is a simple/trivial/non-controversial change, then one of the Bitcoin development team members simply pulls it.

If it is a more complicated or potentially controversial change, then the patch submitter will be asked to start a discussion (if they haven't already) on the mailing list

The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if the code doesn't match the project's coding conventions (see doc/ or are controversial.

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.


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

Every pull request is built for both Windows and Linux on a dedicated server, and unit and sanity tests are automatically run. The binaries produced may be used for manual QA testing — a link to them will appear in a comment on the pull request posted by BitcoinPullTester. See for the build/test scripts.

Manual Quality Assurance (QA) Testing

Large changes should have a test plan, and should be tested by somebody other than the developer who wrote the code. See for how to create a test plan.


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.

You can’t perform that action at this time.