You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
fanquake 0e209f9bf9
[trivial] Sync ax_pthread with upstream draft
5 anni fa
.tx qt: translation update prior to opening 0.12 translations 6 anni fa
build-aux/m4 [trivial] Sync ax_pthread with upstream draft 5 anni fa
contrib build: add armhf/aarch64 gitian builds 5 anni fa
depends build: add armhf/aarch64 gitian builds 5 anni fa
doc [trivial][doc] Use Debian 8.5 in the gitian-build guide 5 anni fa
qa Merge #8141: Continuing port of java comparison tool 5 anni fa
share build: Get rid of `CLIENT_DATE` 5 anni fa
src Merge #8141: Continuing port of java comparison tool 5 anni fa
.gitattributes Separate protocol versioning from clientversion 7 anni fa
.gitignore Merge pull request #6813 6 anni fa
.travis.yml Merge #8067: travis: use slim generic image, and some fixups 5 anni fa
CONTRIBUTING.md [doc] Add basic git squash example 5 anni fa
COPYING Update license year range to 2016 5 anni fa
INSTALL Prettify some /Contrib READMEs 8 anni fa
Makefile.am build: add temporary fix for "bad magic number" error in out-of-tree builds 5 anni fa
README.md changing "(tests are) automatically run" to correspond to the earlier instance of "run automatically (on the build server)" 5 anni fa
autogen.sh autogen.sh: warn about needing autoconf if autoreconf is not found 5 anni fa
configure.ac build: add armhf/aarch64 gitian builds 5 anni fa
libbitcoinconsensus.pc.in Unify package name to as few places as possible without major changes 5 anni fa

README.md

Bitcoin Core integration/staging tree

Build Status

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

License

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

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, 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.

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.