Du kannst nicht mehr als 25 Themen auswählen Themen müssen mit entweder einem Buchstaben oder einer Ziffer beginnen. Sie können Bindestriche („-“) enthalten und bis zu 35 Zeichen lang sein.
John Newbery 4550049903 Reorganize BitcoinTestFramework class vor 4 Jahren
.github Mention reporting security issues responsibly vor 5 Jahren
.tx qt: Set transifex slug to 0.14 vor 4 Jahren
build-aux/m4 Run bitcoin_test-qt under minimal QPA platform vor 4 Jahren
contrib Merge #9670: contrib: github-merge improvements vor 4 Jahren
depends depends: fix zlib build on osx vor 4 Jahren
doc Merge #10260: [doc] Minor corrections to osx dependencies vor 4 Jahren
share Fix typos vor 4 Jahren
src Merge #10314: Remove unused forward declaration for non-existent ScriptPubKeyToJSON(...) vor 4 Jahren
test Reorganize BitcoinTestFramework class vor 4 Jahren
.gitattributes Separate protocol versioning from clientversion vor 7 Jahren
.gitignore Move src/test/bitcoin-util-test.py to test/util/bitcoin-util-test.py vor 4 Jahren
.travis.yml [trivial] remove unused line in Travis config vor 4 Jahren
CONTRIBUTING.md [doc] Add blob about finding reviewers. vor 4 Jahren
COPYING [Trivial] Update license year range to 2017 vor 4 Jahren
INSTALL.md Update INSTALL landing redirection notice for build instructions. vor 5 Jahren
Makefile.am build: remove wonky auto top-level convenience targets vor 4 Jahren
README.md Rename test/pull-tester/rpc-tests.py to test/functional/test_runner.py vor 4 Jahren
autogen.sh Add MIT license to autogen.sh and share/genbuild.sh vor 5 Jahren
configure.ac Merge #9792: FastRandomContext improvements and switch to ChaCha20 vor 4 Jahren
libbitcoinconsensus.pc.in Unify package name to as few places as possible without major changes vor 5 Jahren


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 https://bitcoin.org/en/download, or read the original whitepaper.


Bitcoin Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

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 CONTRIBUTING.md.

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/README.md.

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/test_runner.py

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.