Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.
MarcoFalke 23d78c4dd0
Merge #10352: test: Add elapsed time to RPC tracing
il y a 4 ans
.github Mention reporting security issues responsibly il y a 5 ans
.tx qt: Set transifex slug to 0.14 il y a 4 ans
build-aux/m4 Run bitcoin_test-qt under minimal QPA platform il y a 4 ans
contrib devtools: add script to verify scriptable changes il y a 4 ans
depends depends: fix zlib build on osx il y a 4 ans
doc Merge #10260: [doc] Minor corrections to osx dependencies il y a 4 ans
share Fix typos il y a 4 ans
src Merge #10310: [doc] Add hint about getmempoolentry to getrawmempool help. il y a 4 ans
test Merge #10352: test: Add elapsed time to RPC tracing il y a 4 ans
.gitattributes Separate protocol versioning from clientversion il y a 7 ans
.gitignore Move src/test/bitcoin-util-test.py to test/util/bitcoin-util-test.py il y a 4 ans
.travis.yml devtools: add script to verify scriptable changes il y a 4 ans
CONTRIBUTING.md [doc] Add blob about finding reviewers. il y a 4 ans
COPYING [Trivial] Update license year range to 2017 il y a 4 ans
INSTALL.md Update INSTALL landing redirection notice for build instructions. il y a 5 ans
Makefile.am build: remove wonky auto top-level convenience targets il y a 4 ans
README.md Rename test/pull-tester/rpc-tests.py to test/functional/test_runner.py il y a 4 ans
autogen.sh Add MIT license to autogen.sh and share/genbuild.sh il y a 5 ans
configure.ac Merge #9792: FastRandomContext improvements and switch to ChaCha20 il y a 4 ans
libbitcoinconsensus.pc.in Unify package name to as few places as possible without major changes il y a 6 ans


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.