sikkienl/dash
1
0
Fork 0
mirror of https://github.com/dashpay/dash.git synced 2024-12-25 12:02:48 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity
Dash - Reinventing Cryptocurrency
16,721 Commits 24 Branches 554 Tags 573 MiB
C++ 52.7%
C 24.2%
Python 10.5%
Assembly 3.3%
JavaScript 2.6%
Other 6.5%
b9ce8480df
Go to file
Pieter Wuille b9ce8480df Merge #11215: [tests] fixups from set_test_params() 
3918d93f3 [tests] fixups from set_test_params() (John Newbery)

Pull request description:

  #11121 had a silent merge conflict in `bitcoin_cli.py`. This fixes it.

  Also fixes a comment in `example_test.py`

Tree-SHA512: f22a645c51c9aeda005526338ad6f2ee07f2bab172847fc54f51fecf1c79e778970be61e5e637d4e0aba3a02e5aba0737b0b57f1bc11a514a1acd94c221b54d6
2019-09-24 17:47:35 +02:00
.github Add link to bugcrowd in issue template (#2716) 2019-02-19 13:05:59 +03:00
.tx
build-aux/m4 Merge #10803: Explicitly search for bdb5.3. 2019-07-24 11:59:09 -05:00
ci adjust build_src.sh 10189 2019-06-19 12:44:42 -05:00
contrib Merge #11097: gitian: quick hack to fix version string in releases 2019-09-23 20:49:54 +02:00
depends Add OpenSSL termios fix for musl libc (#3099) 2019-09-22 23:47:02 +03:00
doc Merge #11119: [doc] build-windows: Mention that only trusty works 2019-09-23 20:49:54 +02:00
docker
share Update/modernize macOS plist (#3074) 2019-09-03 22:48:14 +03:00
src Merge #10859: RPC: gettxout: Slightly improve doc and tests 2019-09-24 16:58:03 +02:00
test Merge #11215: [tests] fixups from set_test_params() 2019-09-24 17:47:35 +02:00
.gitattributes
.gitignore bitcoin -> dash 2019-08-24 11:11:25 -05:00
.travis.yml Fix 2 common Travis failures which happen when Travis has network issues (#3003) 2019-06-27 23:25:30 +03:00
autogen.sh
CMakeLists.txt Enable stacktrace support in gitian builds (#3006) 2019-07-02 07:16:11 +03:00
configure.ac Ensure execinfo.h and linker flags set in autoconf (#3098) 2019-09-22 23:46:45 +03:00
CONTRIBUTING.md Merge #11003: Docs: Capitalize bullet points in CONTRIBUTING guide 2019-08-12 09:07:03 -05: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
Makefile.am Merge #10565: [coverage] Remove subtrees and benchmarks from coverage report 2019-07-11 10:34:46 -05:00
README.md Merge bitcoin#9956: Reorganise qa directory (#2912) 2019-05-19 23:20:34 +03:00

README.md

Dash Core staging tree 0.14.1

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, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: test/functional/test_runner.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.