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.
Pieter Wuille 3743b80528 Merge pull request #3430 from ldenman/patch-1 8 years ago
contrib Fix file hash verification error in deps-win32.yml 8 years ago
doc Fix typo in 8 years ago
qa Integration tests via RPC calls 8 years ago
share [Qt] misc small Mac related changes/cleanups 8 years ago
src qt: Update English language file for translators 8 years ago
.gitattributes Build identification strings 9 years ago
.gitignore .gitignore: Simplify references to the same file in different directories 8 years ago
COPYING Bump version numbers for 0.8 release 8 years ago
INSTALL Prettify some /Contrib READMEs 8 years ago Fix port binding by listening on port $BASHPID 8 years ago Documentation Cleanup in /Doc 8 years ago Stop passing --verbose to autoreconf 8 years ago build: fix syntax error on older m4/autoconf. 8 years ago
pkg.m4 autotools: switch to autotools buildsystem 8 years ago

Bitcoin integration/staging tree

Copyright © 2009-2013 Bitcoin 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 is also the name of the open source software which enables the use of this currency.

For more information, as well as an immediately useable, binary version of the Bitcoin client software, see


Bitcoin 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.