C++ C Python CSS M4 Makefile Other
Clone or download
Pull request Compare This branch is 5138 commits ahead, 8266 commits behind bitcoin:master.
UdjinM6 Release notes (#2174)
* Archive release notes

* Release notes

* add 2175

* add 2176
Latest commit 855ac35 Jul 9, 2018
Failed to load latest commit information.
.github Use "Dash Core" instead of "dash-core" in some places and Dashify Jan 16, 2018
.tx Merge remote-tracking branch 'bitcoin/0.12' into HEAD Feb 6, 2016
build-aux/m4 Merge #9705: build: Add options to override BDB cflags/libs Jan 23, 2018
contrib Update/optimize images (#2147) Jun 28, 2018
dash-docs Update protocol-documentation.md (#1964) Mar 2, 2018
depends Merge #9114: [depends] Set OSX_MIN_VERSION to 10.8 Feb 7, 2018
doc Release notes (#2174) Jul 9, 2018
docker Automatically build and push docker image to docker.io/dashpay/dashd-… Jan 10, 2018
qa Fix rpc tests broken by 2110 (#2118) Jun 12, 2018
share Update/optimize images (#2147) Jun 28, 2018
src Add tests for special rules for slow blocks on devnet/testnet (#2176) Jul 9, 2018
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.gitignore Add dummy CMakeLists.txt file to make development with CLion easier (#… Mar 9, 2018
.travis.yml Fix use of distdir and docker build dir Jan 21, 2018
CMakeLists.txt Add dummy CMakeLists.txt file to make development with CLion easier (#… Mar 9, 2018
CONTRIBUTING.md Merge #9675: Fix typo and spelling inconsistency in CONTRIBUTING.md Jan 23, 2018
COPYING Merge #9617: [Trivial] Update license year range to 2017 Jan 21, 2018
INSTALL.md Dashify INSTALL.md and build-unix.md Jan 12, 2018
Makefile.am Merge #10228: build: regenerate bitcoin-config.h as necessary Jan 26, 2018
README.md Update release notes and staging tree in README (#2116) Jun 12, 2018
autogen.sh Merge #8784: Copyright headers for build scripts Jan 12, 2018
configure.ac Bump to (#2173) Jul 7, 2018
libdashconsensus.pc.in Merge #7192: Unify product name to as few places as possible Dec 11, 2017


Dash Core staging tree 0.12.3

master: Build Status develop: Build Status


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


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


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.