Du kan inte välja fler än 25 ämnen Ämnen måste starta med en bokstav eller siffra, kan innehålla bindestreck ('-') och vara max 35 tecken långa.
Pieter Wuille 6851107b3a BIP9 Implementation 5 år sedan
.tx qt: translation update prior to opening 0.12 translations 5 år sedan
build-aux/m4 Merge #7604: build: Remove spurious dollar sign. Fixes #7189. 5 år sedan
contrib Delete outdated test-patches reference 5 år sedan
depends Merge #7616: [depends] Delete unused patches 5 år sedan
doc Add curl to Gitian setup instrustions 5 år sedan
qa Check if zmq is installed in tests, update docs 5 år sedan
share [doc] Fix markdown 5 år sedan
src BIP9 Implementation 5 år sedan
.gitattributes Separate protocol versioning from clientversion 6 år sedan
.gitignore Merge pull request #6813 5 år sedan
.travis.yml [travis] Exit early when check-doc.py fails 5 år sedan
CONTRIBUTING.md Note that reviewers should mention the commit hash of the commits they reviewed. 5 år sedan
COPYING Update license year range to 2016 5 år sedan
INSTALL Prettify some /Contrib READMEs 7 år sedan
Makefile.am Merge branch 'master' into single_prodname 5 år sedan
README.md Check if zmq is installed in tests, update docs 5 år sedan
autogen.sh autogen.sh: warn about needing autoconf if autoreconf is not found 5 år sedan
configure.ac Merge #7349: Build against system UniValue when available 5 år sedan
libbitcoinconsensus.pc.in Unify package name to as few places as possible without major changes 5 år sedan


Bitcoin Core integration/staging tree

Build Status


What is Bitcoin?

Bitcoin is an experimental new 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

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/rpc-tests.py

The Travis CI system makes sure that every pull request is built for Windows and Linux, OS X, and that unit and sanity tests are automatically run.

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.