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.
Pieter Wuille eece63fa72 Switch blocks to a constant-space Merkle root/branch algorithm. il y a 5 ans
.tx qt: translation update prior to opening 0.12 translations il y a 5 ans
build-aux/m4 build: Use fPIC rather than fPIE for qt objects. il y a 5 ans
contrib Merge pull request #7042 il y a 5 ans
depends Merge pull request #7059 il y a 5 ans
doc Connect to Tor hidden services by default il y a 5 ans
qa Merge pull request #6871 il y a 5 ans
share [trivial] Remove obsolete share/qt/make_windows_icon.sh il y a 5 ans
src Switch blocks to a constant-space Merkle root/branch algorithm. il y a 5 ans
.gitattributes Separate protocol versioning from clientversion il y a 6 ans
.gitignore Merge pull request #6813 il y a 5 ans
.travis.yml Add basic coverage reporting for RPC tests il y a 5 ans
CONTRIBUTING.md Add PR title prefix for trivial changes [skip ci] il y a 5 ans
COPYING Update contrib/debian/copyright il y a 5 ans
INSTALL Prettify some /Contrib READMEs il y a 7 ans
Makefile.am build: Set osx permissions in the dmg to make Gatekeeper happy il y a 5 ans
README.md [qa] Extend README.md il y a 5 ans
autogen.sh Bugfix: Replace bashisms with standard sh to fix build on non-BASH systems il y a 6 ans
configure.ac Update key.cpp to new secp256k1 API il y a 5 ans
libbitcoinconsensus.pc.in libbitcoinconsensus: Add pkg-config support il y a 6 ans

README.md

Bitcoin Core integration/staging tree

Build Status

https://www.bitcoin.org

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.

License

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

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.

Translations

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.