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.
Kamil Domanski 3e74ac22d5 json_spirit: #include <stdint.h> 7 years ago
.tx qt: add transifex configuration file 7 years ago
contrib doc: remove mention of `-rpctimeout` from man page 7 years ago
doc doc: remove specific mention of boost 1.55 7 years ago
qa Add Python test for -rpcbind and -rpcallowip 7 years ago
share build: fix: remove error output 7 years ago
src json_spirit: #include <stdint.h> 7 years ago
.gitattributes Build identification strings 9 years ago
.gitignore Ignore temporary object files 7 years ago
COPYING Bump version numbers for 0.8 release 8 years ago
INSTALL Prettify some /Contrib READMEs 8 years ago build: fix make clean on OSX 7 years ago doc: add note about translations to 7 years ago Stop passing --verbose to autoreconf 8 years ago Remove build-time no-IPv6 setting 7 years ago
pkg.m4 autotools: switch to autotools buildsystem 8 years ago

Bitcoin Core integration/staging tree

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