No description, website, or topics provided.
Switch branches/tags
Nothing to show
Clone or download
dacash-publisher Set SPORK_8_MASTERNODE_PAYMENT_ENFORCEMENT_DEFAULT (to elaborate yiim…
…p pool bug)

Popular yiimp pool has a bug with identification of masternode payments.
It includes such payment only if masternode payments are enforced.
It should NOT be required to have such enforcement to pay to masternodes.
The existance of masternode object and masternode_payments_started
binary flag should be enough to pay. But yiimp will only pay if another
binary flag masternode_payments_enforced is set. Otherwise no blocks
with missing masternode payments will be accepted by the network.

This commit sets the default value according to the de-facto timestamp
after block 10000 (masternode payment start block).
Latest commit 6d7fab7 Jun 25, 2018

README.md

DACash Core staging tree 1.0.0

master: Build Status develop: Build Status

https://www.dacash.org

What is DACash?

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

License

DACash 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 DACash 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 (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 and Linux, OS X, 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.

Translations

Changes to translations as well as new translations can be submitted to DACash 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.