- Notifications
You must be signed in to change notification settings - Fork1.2k
Dash - Reinventing Cryptocurrency
License
dashpay/dash
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
CI | master | develop |
---|---|---|
Gitlab |
For an immediately usable, binary version of the Dash Core software, seehttps://www.dash.org/downloads/.
Further information about Dash Core is available in./doc/.
Dash is an experimental digital currency that enables instant, privatepayments to anyone, anywhere in the world. Dash uses peer-to-peer technologyto operate with no central authority: managing transactions and issuing moneyare carried out collectively by the network. Dash Core is the name of the opensource software which enables the use of this currency.
For more information read the original Dash whitepaper.
Dash Core is released under the terms of the MIT license. SeeCOPYING for moreinformation or seehttps://opensource.org/licenses/MIT.
Themaster
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.
Thedevelop
branch is regularly built (see doc/build-*.md for instructions) and tested, but is not guaranteed to becompletely stable.
The contribution workflow is described inCONTRIBUTING.mdand useful hints for developers can be found indoc/developer-notes.md.
The./configure
,make
, andcmake
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 and code review is the bottleneck for development; we get more pullrequests than we can review and test on short notice. Please be patient and help out by testingother people's pull requests, and remember this is a security-critical project where any mistake might cost peoplelots of money.
Developers are strongly encouraged to writeunit tests for new code, and tosubmit 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 runningand extending unit tests can be found in/src/test/README.md.
There are alsoregression and integration tests, writtenin Python.These tests can be run (if thetest dependencies are installed) with: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.
Changes should be tested by somebody other than the developer who wrote thecode. This is especially important for large or high-risk changes. It is usefulto add a test plan to the pull request description if testing the changes isnot straightforward.
Changes to translations as well as new translations can be submitted toDash Core's Transifex page.
Translations are periodically pulled from Transifex and merged into the git repository. See thetranslation process for details on how this works.
Important: We do not accept translation changes as GitHub pull requests because the nextpull from Transifex would automatically overwrite them again.
About
Dash - Reinventing Cryptocurrency
Topics
Resources
License
Security policy
Stars
Watchers
Forks
Languages
- C++53.6%
- C23.4%
- Python10.5%
- Assembly3.3%
- JavaScript2.6%
- HTML2.1%
- Other4.5%