Bitcoin Core UASF BIP148. Download:
Clone or download
Pull request Compare This branch is 164 commits ahead, 6056 commits behind bitcoin:master.
Latest commit 2e7690f Jul 9, 2017
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Mention reporting security issues responsibly Nov 10, 2016
.tx qt: Set transifex slug to 0.14 Jan 2, 2017
build-aux/m4 build: force a c++ standard to be specified Feb 23, 2017
contrib Fix regsig checking for subkey sigs in verify-commits Mar 5, 2017
depends [depends] miniupnpc 2.0.20170509 May 17, 2017
doc Merge branch 'uasfsegwit+bips' of Jun 20, 2017
qa Merge branch 'uasfsegwit+bip148_test' of… Jul 8, 2017
share Fix typos Jan 29, 2017
src bump UASF version to 1.0 Jul 8, 2017
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.gitignore gitignore: Wipe line after java comp tool removal Dec 20, 2016
.travis.yml Test that pushes to bitcoin/bitcoin are signed per verify-commits Feb 1, 2017 Merge bitcoin#9675: Fix typo and spelling inconsistency in CONTRIBUTI… Feb 16, 2017
COPYING [Trivial] Update license year range to 2017 Jan 23, 2017 Update INSTALL landing redirection notice for build instructions. Oct 5, 2016 build: remove wonky auto top-level convenience targets May 31, 2017 Merge `doc/` into `src/test/` Nov 2, 2016 Add MIT license to and share/ Sep 21, 2016 build: bump version to 0.14.2 Jun 2, 2017 Unify package name to as few places as possible without major changes Dec 14, 2015

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 of the RPC interface, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: qa/pull-tester/

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.