No description, website, or topics provided.
Switch branches/tags
Nothing to show
Clone or download
Latest commit 387b744 Oct 2, 2017
Permalink
Failed to load latest commit information.
.tx v.0.12.1.5 Oct 2, 2017
build-aux/m4 v.0.12.1.5 Oct 2, 2017
contrib v.0.12.1.5 Oct 2, 2017
das-docs v.0.12.1.5 Oct 2, 2017
depends v.0.12.1.5 Oct 2, 2017
doc v.0.12.1.5 Oct 2, 2017
qa v.0.12.1.5 Oct 2, 2017
share v.0.12.1.5 Oct 2, 2017
src Delete build-aux\m4 Oct 2, 2017
.gitattributes 🍭 Added .gitattributes & .gitignore files Oct 2, 2017
.gitignore 🍭 Added .gitattributes & .gitignore files Oct 2, 2017
.travis.yml v.0.12.1.5 Oct 2, 2017
CONTRIBUTING.md v.0.12.1.5 Oct 2, 2017
COPYING v.0.12.1.5 Oct 2, 2017
INSTALL v.0.12.1.5 Oct 2, 2017
Makefile.am v.0.12.1.5 Oct 2, 2017
README.md v.0.12.1.5 Oct 2, 2017
autogen.sh v.0.12.1.5 Oct 2, 2017
configure.ac v.0.12.1.5 Oct 2, 2017
libbitcoinconsensus.pc.in v.0.12.1.5 Oct 2, 2017

README.md

Das Core staging tree 0.12.1.5

Official Forum.

What is Das?

Das is an experimental new digital currency that enables anonymous, instant payments to anyone, anywhere in the world. Das uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Das 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 Das Core software, see https://github.com/Truckman83/DAS-source/releases.

License

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

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 with: qa/pull-tester/rpc-tests.py

The Travis CI system makes sure that every pull request is built for Windows and Linux, OSX, and that unit and sanity tests are automatically run.

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.