Ви не можете вибрати більше 25 тем Теми мають розпочинатися з літери або цифри, можуть містити дефіси (-) і не повинні перевищувати 35 символів.
Pieter Wuille eece63fa72 Switch blocks to a constant-space Merkle root/branch algorithm. 5 роки тому
.tx qt: translation update prior to opening 0.12 translations 5 роки тому
build-aux/m4 build: Use fPIC rather than fPIE for qt objects. 5 роки тому
contrib Merge pull request #7042 5 роки тому
depends Merge pull request #7059 5 роки тому
doc Connect to Tor hidden services by default 5 роки тому
qa Merge pull request #6871 5 роки тому
share [trivial] Remove obsolete share/qt/make_windows_icon.sh 5 роки тому
src Switch blocks to a constant-space Merkle root/branch algorithm. 5 роки тому
.gitattributes Separate protocol versioning from clientversion 6 роки тому
.gitignore Merge pull request #6813 5 роки тому
.travis.yml Add basic coverage reporting for RPC tests 5 роки тому
CONTRIBUTING.md Add PR title prefix for trivial changes [skip ci] 5 роки тому
COPYING Update contrib/debian/copyright 5 роки тому
INSTALL Prettify some /Contrib READMEs 7 роки тому
Makefile.am build: Set osx permissions in the dmg to make Gatekeeper happy 5 роки тому
README.md [qa] Extend README.md 5 роки тому
autogen.sh Bugfix: Replace bashisms with standard sh to fix build on non-BASH systems 6 роки тому
configure.ac Update key.cpp to new secp256k1 API 5 роки тому
libbitcoinconsensus.pc.in libbitcoinconsensus: Add pkg-config support 6 роки тому


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://www.bitcoin.org/en/download.


Bitcoin Core is released under the terms of the MIT license. See COPYING for more information or see http://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 with: qa/pull-tester/rpc-tests.py

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