Dash - Reinventing Cryptocurrency
Go to file
Wladimir J. van der Laan f4d30a6452 Merge #7708: De-neuter NODE_BLOOM
c90036f Always disconnect old nodes which request filtered connections. (Patrick Strateman)
2017-12-19 12:55:49 +01:00
.tx Merge remote-tracking branch 'bitcoin/0.12' into HEAD 2016-02-06 16:48:04 +03:00
build-aux/m4 Merge pull request #1770 from codablock/pr_backport_bitcoin_0.12-1 2017-12-19 14:41:47 +03:00
contrib Merge #7632: Delete outdated test-patches reference 2017-12-11 08:30:26 +01:00
dash-docs [Trivial] Typo/doc updates and RPC help formatting (#1758) 2017-12-06 01:17:45 +03:00
depends Merge #8373: Fix OSX non-deterministic dmg 2017-12-11 08:30:26 +01:00
doc Merge #7708: De-neuter NODE_BLOOM 2017-12-19 12:55:49 +01:00
qa Merge #7635: [Documentation] Add dependency info to test docs 2017-12-19 12:55:49 +01:00
share Merge #7192: Unify product name to as few places as possible 2017-12-11 08:30:26 +01:00
src Merge #7708: De-neuter NODE_BLOOM 2017-12-19 12:55:49 +01:00
.gitattributes Separate protocol versioning from clientversion 2014-10-29 00:24:40 -04:00
.gitignore Rename bitcoinconsensus library to dashconsensus. (#1432) 2017-04-15 09:29:09 +02:00
.travis.yml Disable check-doc.py for now until all backported PRs are merged and docs fixed 2017-12-11 08:30:26 +01:00
autogen.sh Merge #7528: autogen.sh: warn about needing autoconf if autoreconf is not found 2017-12-11 08:30:26 +01:00
configure.ac Merge pull request #1770 from codablock/pr_backport_bitcoin_0.12-1 2017-12-19 14:41:47 +03:00
CONTRIBUTING.md Doc: fix broken formatting in markdown #headers (#1462) 2017-05-05 14:28:08 +03:00
COPYING bump copyright notice to 2017 (#1207) 2016-12-20 17:26:45 +04:00
INSTALL Added clarifications in INSTALL readme for newcomers (#1481) 2017-05-31 06:50:03 +03:00
libdashconsensus.pc.in Merge #7192: Unify product name to as few places as possible 2017-12-11 08:30:26 +01:00
Makefile.am Merge #7192: Unify product name to as few places as possible 2017-12-11 08:30:26 +01:00
README.md Bump version in README.md to 0.12.2 (#1774) 2017-12-12 12:53:44 +03:00

Dash Core staging tree 0.12.2

master: Build Status develop: Build Status

https://www.dash.org

What is Dash?

Dash is an experimental new digital currency that enables anonymous, instant payments to anyone, anywhere in the world. Dash uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Dash Core is the name of the open source software which enables the use of this currency.

For more information, as well as an immediately useable, binary version of the Dash Core software, see https://www.dash.org/get-dash/.

License

Dash 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 meant to be stable. Development is normally done in separate branches. Tags are created to indicate new official, stable release versions of Dash Core.

The contribution workflow is described in CONTRIBUTING.md.

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 Dash 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 follow the forum.