Bitcoin Core integration/staging tree
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.
Andrew Chow 461b9b11b2
Update Windows code signing certificate
1 year ago
.github doc: Put PR template in comments 3 years ago
.tx gui: Update transifex slug for 0.19 3 years ago
build-aux/m4 build: Fix boost detection on Ubuntu ARM 18.04 3 years ago
build_msvc build: Bump version to 0.19.2rc1 2 years ago
ci lint: fix shellcheck URL in CI install 2 years ago
contrib Update Windows code signing certificate 1 year ago
depends qt: Fix QFileDialog for static builds 2 years ago
doc doc: Update release notes for 0.19.2 2 years ago
share doc: Fix whitespace errs in .md files, bitcoin.conf,, and find_bdb48.m4 3 years ago
src gui: Pre-rc1 translations update 2 years ago
test test addition of unknown segwit spends to txid reject filter 2 years ago
.appveyor.yml Bump vcpkg commit ID to get new msys mirror list 2 years ago
.cirrus.yml test: remove Cirrus CI FreeBSD job 2 years ago
.gitattributes Separate protocol versioning from clientversion 8 years ago
.gitignore Merge #16371: build: ignore macOS make deploy artefacts & add them to clean-local 3 years ago
.python-version .python-version: Specify full version 3.5.6 4 years ago
.style.yapf test: .style.yapf: Set column_limit=160 4 years ago
.travis.yml Enable UBSan for Travis fuzzer job 3 years ago doc: Update labels in 3 years ago
COPYING [Trivial] Update license year range to 2019 4 years ago Update INSTALL landing redirection notice for build instructions. 6 years ago build: ignore macOS make deploy artefacts & add them to clean-local 3 years ago doc: Remove travis badge from readme 3 years ago doc: Remove explicit mention of version from 3 years ago Enable ShellCheck rules 3 years ago build: Bump rc to final 2 years ago Unify package name to as few places as possible without major changes 7 years ago

Bitcoin Core integration/staging tree

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 and useful hints for developers can be found in doc/


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

The Travis CI system makes sure that every pull request is built for Windows, Linux, and macOS, 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.