Nelze vybrat více než 25 témat Téma musí začínat písmenem nebo číslem, může obsahovat pomlčky („-“) a může být dlouhé až 35 znaků.
Suhas Daftuar b5fd666984 [qa] Fix race condition in p2p-compactblocks test před 5 roky
.github Adds issue template. [skip ci] před 5 roky
.tx tx: change slug to `bitcoin.qt-translation-013x` před 5 roky
build-aux/m4 Add configure check for -latomic před 5 roky
contrib Merge #8779: [contrib] Delete spendfrom před 5 roky
depends [depends] fontconfig 2.12.1 před 5 roky
doc Merge #8773: Trivial Bugfix: doc/ Link to release-process needs to be updated před 5 roky
qa [qa] Fix race condition in p2p-compactblocks test před 5 roky
share [share] remove qt/protobuf.pri před 5 roky
src Merge #8790: [test] Remove redundant debug print in addrman_tests před 5 roky
.gitattributes Separate protocol versioning from clientversion před 7 roky
.gitignore gitignore: Remove unused lines před 5 roky
.travis.yml [travis] Drop java před 5 roky Fix formatting před 5 roky
COPYING Update license year range to 2016 před 5 roky
INSTALL Prettify some /Contrib READMEs před 8 roky add doc/man to subdir if configure flag --enable-man is set před 5 roky readme: Omit phrasing; 'new' před 5 roky warn about needing autoconf if autoreconf is not found před 5 roky Merge #8608: Install manpages via make install, also add some autogenerated manpages před 5 roky Unify package name to as few places as possible without major changes před 6 roky

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

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.