Dash - Reinventing Cryptocurrency
Go to file
UdjinM6 c74f2cd8b2 Fix SelectCoinsMinConf to allow instant respends (#3061)
* Modify tests to check for instant respends

This should fail atm...

* Fix SelectCoinsMinConf to allow instant respends

Now tests should pass again.
2019-11-18 15:28:19 +01:00
.github Add link to bugcrowd in issue template (#2716) 2019-02-19 13:05:59 +03:00
.tx Merge remote-tracking branch 'bitcoin/0.12' into HEAD 2016-02-06 16:48:04 +03:00
build-aux/m4 Merge #9705: build: Add options to override BDB cflags/libs 2018-01-23 09:24:28 +01:00
ci Fix qt tests and actually run them (#2801) 2019-03-25 19:24:24 +03:00
contrib Merge pull request #3028 from PastaPastaPasta/backport-12588 2019-08-07 12:19:49 +02:00
depends Fix 2 common Travis failures which happen when Travis has network issues (#3003) 2019-07-02 06:41:10 +02:00
doc Add 0.14.0.3 change log to release-notes.md (#3055) 2019-08-14 04:51:13 +02:00
docker Automatically build and push docker image to docker.io/dashpay/dashd-develop (#1809) 2018-01-10 12:17:43 +03:00
qa Fix SelectCoinsMinConf to allow instant respends (#3061) 2019-11-18 15:28:19 +01:00
share Backport #12783: macOS: disable AppNap during sync (and mixing) (#3024) 2019-08-07 12:19:49 +02:00
src Fix SelectCoinsMinConf to allow instant respends (#3061) 2019-11-18 15:28:19 +01:00
.gitattributes Separate protocol versioning from clientversion 2014-10-29 00:24:40 -04:00
.gitignore Fix 2 common Travis failures which happen when Travis has network issues (#3003) 2019-07-02 06:41:10 +02:00
.travis.yml Fix 2 common Travis failures which happen when Travis has network issues (#3003) 2019-07-02 06:41:10 +02:00
autogen.sh Merge #8784: Copyright headers for build scripts 2018-01-12 08:02:45 +01:00
CMakeLists.txt Add src/bls/*.h and .cpp to CMakeLists.txt 2019-01-17 18:51:47 +01:00
configure.ac Bump version to 0.14.0.3 and copy release notes (#3053) 2019-08-12 20:08:33 +02:00
CONTRIBUTING.md add link for developer-notes in contributing (#2260) 2018-09-05 15:05:27 +03:00
COPYING update copyright (#2648) 2019-01-29 15:53:14 +01:00
INSTALL.md Dashify INSTALL.md and build-unix.md 2018-01-12 16:12:54 +01:00
Jenkinsfile Perform Jenkins builds in /dash-src all the time to fix caching issues (#2242) 2018-08-29 13:03:18 +03:00
Jenkinsfile.gitian Let ccache compress the cache by itself instead of compressing ccache.tar (#2456) 2018-11-19 07:31:13 +01: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 Backports 0.15 pr1 (#2590) 2019-01-03 12:18:47 +03:00
README.md Bump version to 0.14 (#2589) 2018-12-28 19:12:52 +03:00

Dash Core staging tree 0.14.0

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.