Bitcoin Core integration/staging tree
Clone or download
MarcoFalke Merge #14411: [wallet] Restore ability to list incoming transactions …
…by label

da427db Rename ListTransactions filter variable (Russell Yanofsky)
65b740f [wallet] Restore ability to list incoming transactions by label (Russell Yanofsky)

Pull request description:

  This change partially reverts #13075 and #14023.

  Fixes #14382

Tree-SHA512: 8c4e56104b3a45784cdc06bae8e5facdfff04fe3545b63a35e0ec2e440a41b79d84833ca4c4e728d8af7ebb8a519303a9eda7bee4bbfb92bd50c58587a33eb30
Latest commit e74649e Nov 14, 2018
Failed to load latest commit information.
.github doc: Add GitHub pr template Sep 23, 2018
.travis travis: Avoid timeout on verify-commits check Nov 10, 2018
.tx tx: Update transifex slug 016x→017x Aug 2, 2018
build-aux/m4 Bump the minimum Qt version to 5.2 Nov 13, 2018
build_msvc Add skeleton chain and client classes Nov 6, 2018
contrib Merge #14611: docs: align items in contrib init Nov 7, 2018
depends build: Remove illegal spacing in Nov 3, 2018
doc Merge #14704: doc: add detached release notes for #14060 Nov 14, 2018
share Merge #14698: build: Add bitcoin-tx.exe into Windows installer Nov 14, 2018
src Merge #14411: [wallet] Restore ability to list incoming transactions … Nov 14, 2018
test [wallet] Restore ability to list incoming transactions by label Nov 13, 2018
.appveyor.yml appveyor: Script improvement part II Nov 6, 2018
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.gitignore gitignore contents of db4 folder Oct 19, 2018
.travis.yml Add llvm-symbolizer directory to PATH. Needed to get symbolized stack… Nov 6, 2018 added details about commit messages Oct 30, 2018
COPYING [Trivial] Update license year range to 2018 Dec 31, 2017 Update INSTALL landing redirection notice for build instructions. Oct 5, 2016 build: Add bitcoin-tx.exe into Windows installer Nov 9, 2018 [doc] conf: Remove deprecated options from docs, Other cleanup Nov 7, 2018 Add "export LC_ALL=C" to all shell scripts Jun 14, 2018 build: Add --disable-bip70 configure option Oct 9, 2018 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 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.