Dash - Reinventing Cryptocurrency
Go to file
Wladimir J. van der Laan 44fdacc19f
Merge #8185: [0.12.2] Various qa and test backports
dc38a53 [qa] Move create_tx() to util.py (MarcoFalke)
c0fe8b5 [qa] smartfees: Properly use ordered dict (MarcoFalke)
493b89e [qa] test_framework: Properly print exceptions and assert empty dict (MarcoFalke)
7a83489 Tests: Fix deserialization of reject messages (Suhas Daftuar)
e0b1bbe [qa] pull-tester: Don't mute zmq ImportError (MarcoFalke)
697ed8c Check if zmq is installed in tests, update docs (Elliot Olds)
d5a9de3 tests: Check Content-Type header returned from RPC server (Wladimir J. van der Laan)
ed2f0e3 [qa] maxblocksinflight: Actually enable test (MarcoFalke)
3036282 [qa] httpbasics: Actually test second connection (MarcoFalke)
afbc000 test_framework: python3.4 authproxy compat (Wladimir J. van der Laan)
80b6bfa test_framework: detect failure of bitcoind startup (Wladimir J. van der Laan)
4ffd309 Create SingleNodeConnCB class for RPC tests (Alex Morcos)
4fd6008 travis: 'make check' in parallel and verbose (Cory Fields)
2d2b045 Reenable multithread scheduler test (Pavel Janík)
658307e test: Add more thorough test for dbwrapper iterators (Wladimir J. van der Laan)
2016-06-20 14:06:16 +02:00
.tx qt: translation update prior to opening 0.12 translations 2015-11-01 16:11:50 +01:00
build-aux/m4 Remove spurious dollar sign. Fixes #7189. 2016-04-27 22:34:48 +02:00
contrib OSX diskimages need 0775 folder permissions 2016-06-09 10:52:43 +02:00
depends travis: switch to Trusty 2016-04-27 12:29:56 +02:00
doc Merge #7938: [0.12.2] Backports 2016-06-09 10:22:52 +02:00
qa [qa] Move create_tx() to util.py 2016-06-10 00:33:26 +02:00
share [doc/log] Fix markdown syntax and line terminate LogPrint 2016-03-11 09:44:17 +01:00
src Reenable multithread scheduler test 2016-06-09 22:52:04 +02:00
.gitattributes Separate protocol versioning from clientversion 2014-10-29 00:24:40 -04:00
.gitignore Merge pull request #6813 2015-10-26 09:09:33 +01:00
.travis.yml travis: 'make check' in parallel and verbose 2016-06-09 23:30:18 +02:00
autogen.sh
configure.ac build: Remove unnecessary executables from gitian release 2016-04-05 15:45:38 +02:00
CONTRIBUTING.md Note that reviewers should mention the commit hash of the commits they reviewed. 2016-01-13 21:25:35 +00:00
COPYING Update license year range to 2016 2016-01-18 10:31:30 +01:00
INSTALL
libbitcoinconsensus.pc.in libbitcoinconsensus: Add pkg-config support 2014-11-20 21:23:34 +00:00
Makefile.am release: Add security/export checks to gitian and fix current failures 2016-01-27 11:33:33 +01:00
README.md Check if zmq is installed in tests, update docs 2016-06-10 00:07:50 +02:00

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

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.