Dash - Reinventing Cryptocurrency
Go to file
Wladimir J. van der Laan d88030845d Merge #9824: qa: Check return code when stopping nodes
fa4cd2e qa: Check return code when stopping nodes (MarcoFalke)
2018-01-26 12:59:29 +01:00
.github Use "Dash Core" instead of "dash-core" in some places and Dashify 2018-01-16 08:30:14 +01:00
.tx
build-aux/m4 Merge #9705: build: Add options to override BDB cflags/libs 2018-01-23 09:24:28 +01:00
contrib Rename and Dashify .manpages files 2018-01-23 16:08:56 +01:00
dash-docs [Trivial] RPC Typos / markdown formatting (#1830) 2018-01-06 13:05:55 +03:00
depends Add missing lines about ARM in depends/README.md 2018-01-23 09:24:29 +01:00
doc Sync release-notes.md with Bitcoin 0.14 2018-01-23 09:24:29 +01:00
docker Automatically build and push docker image to docker.io/dashpay/dashd-develop (#1809) 2018-01-10 12:17:43 +03:00
qa Merge #9824: qa: Check return code when stopping nodes 2018-01-26 12:59:29 +01:00
share Merge #9651: Fix typos 2018-01-23 09:24:27 +01:00
src Merge #9711: [Trivial] Remove incorrect help message from gettxoutproof() 2018-01-26 12:59:29 +01:00
.gitattributes
.gitignore Merge #9390: travis: make distdir 2018-01-18 07:31:23 +01:00
.travis.yml Fix use of distdir and docker build dir 2018-01-21 14:14:34 +01:00
autogen.sh Merge #8784: Copyright headers for build scripts 2018-01-12 08:02:45 +01:00
configure.ac Merge #9475: Let autoconf detect presence of EVP_MD_CTX_new 2018-01-18 07:33:44 +01:00
CONTRIBUTING.md Merge #9675: Fix typo and spelling inconsistency in CONTRIBUTING.md 2018-01-23 09:24:29 +01:00
COPYING Merge #9617: [Trivial] Update license year range to 2017 2018-01-21 12:48:33 +01:00
INSTALL.md Dashify INSTALL.md and build-unix.md 2018-01-12 16:12:54 +01:00
libdashconsensus.pc.in
Makefile.am Disable contrib/rpm dist 2018-01-18 11:37:40 +01:00
README.md Merge #9065: Merge doc/unit-tests.md into src/test/README.md 2018-01-13 13:44:39 +01: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 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. Further details on running and extending unit tests can be found in /src/test/README.md.

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