Text of github.com › dashpay › dash as Styx crawled it on Nov 20, 2026. The page may have changed since. Only its words are kept, without pictures or layout.

Open the live page

GitHub - dashpay/dash: Dash - Reinventing Cryptocurrency · GitHub

Skip to content You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert Branches Tags Open more actions menu Latest commit History 35,674 Commits 35,674 Commits Folders and files Name Name Last commit message Last commit date .github .github .tx .tx ci ci cmake cmake contrib contrib depends depends doc doc share share src src test test .dockerignore .dockerignore .editorconfig .editorconfig .gitattributes .gitattributes .gitignore .gitignore .python-version .python-version .style.yapf .style.yapf AGENTS.md AGENTS.md CMakeLists.txt CMakeLists.txt CONTRIBUTING.md CONTRIBUTING.md COPYING COPYING INSTALL.md INSTALL.md README.md README.md SECURITY.md SECURITY.md libdashconsensus.pc.in libdashconsensus.pc.in Repository files navigation Dash Core staging tree master develop https://www.dash.org For an immediately usable, binary version of the Dash Core software, see https://www.dash.org/downloads/ .

Dash Core connects to the Dash peer-to-peer network to download and fully validate blocks and transactions. It also includes a wallet and graphical user interface, which can be optionally built. Further information about Dash Core is available in the doc folder . What is Dash? Dash is a digital currency that enables instant, private 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 read the original Dash whitepaper. 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 develop branch is regularly built (see doc/build-*.md for instructions) and tested, but is not guaranteed to be completely stable. The contribution workflow is described in CONTRIBUTING.md and useful hints for developers can be found in doc/developer-notes.md . Build / Compile from Source The CMake build steps, as well as build dependencies, are in ./doc/ as well: Linux : ./doc/build-unix.md Ubuntu, Debian, Fedora, Arch, and others macOS : ./doc/build-osx.md Windows : ./doc/build-windows.md OpenBSD : ./doc/build-openbsd.md FreeBSD : ./doc/build-freebsd.md NetBSD : ./doc/build-netbsd.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. Build with cmake --build build , then run unit tests with ctest --test-dir build (assuming they were not disabled during configuration).

Further details on running and extending unit tests can be found in /src/test/README.md . There are also regression and integration tests , written in Python. These tests can be run (if the test dependencies are installed) with: build/test/functional/test_runner.py The CI (Continuous Integration) systems make sure that every pull request is built for Windows, Linux, and macOS, 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. About Dash - Reinventing Cryptocurrency www.dash.org Topics bitcoin blockchain cryptocurrency dash governance instant masternode p2p privacy Resources Readme MIT license Contributing Contributing Security policy Security policy Activity Custom properties Stars 1.5k stars Watchers 192 watching Forks 1.2k forks Report repository Releases Packages Used by Contributors Languages You can’t perform that action at this time.