Skip to content
This repository

Bitcoin Core integration/staging tree

Merge pull request #4042

05c20a5 build: add symbol for upcoming gcc 4.9's libstdc++ (Cory Fields)
49a3352 gitian-linux: --enable-glibc-back-compat (Warren Togami)
d5aab70 build: add an option for enabling glibc back-compat (Cory Fields)
ffc6b67 build: add glibc/libstdc++ back-compat stubs (Cory Fields)
latest commit bbe53f61db
Wladimir J. van der Laan laanwj authored April 22, 2014
Octocat-spinner-32 contrib Merge pull request #4042 April 22, 2014
Octocat-spinner-32 doc Pointed to location of BDB 4.8 in procedure for unix build. April 16, 2014
Octocat-spinner-32 qa Have pull-tester run the regression test April 02, 2014
Octocat-spinner-32 share VERSION obtained from source instead of the previous git tag. April 15, 2014
Octocat-spinner-32 src Merge pull request #4042 April 22, 2014
Octocat-spinner-32 .gitattributes Build identification strings April 10, 2012
Octocat-spinner-32 .gitignore Ignore temporary object files March 22, 2014
Octocat-spinner-32 COPYING Bump version numbers for 0.8 release January 30, 2013
Octocat-spinner-32 INSTALL Prettify some /Contrib READMEs October 21, 2013
Octocat-spinner-32 Have pull-tester run the regression test April 02, 2014
Octocat-spinner-32 doc: add note about translations to April 11, 2014
Octocat-spinner-32 Stop passing --verbose to autoreconf November 27, 2013
Octocat-spinner-32 build: add an option for enabling glibc back-compat April 10, 2014
Octocat-spinner-32 pkg.m4 autotools: switch to autotools buildsystem September 05, 2013

Bitcoin Core integration/staging tree

Copyright (c) 2009-2014 Bitcoin Core Developers

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. Please be patient and help out, 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.

Periodically the translations are 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 request because the next pull from Transifex would automatically overwrite them again.

Something went wrong with that request. Please try again.