Dinero is a leading edge cryptocurrency focused on speed and privacy www.dinerocoin.org
Clone or download
Permalink
Failed to load latest commit information.
build-aux/m4 base code Jan 16, 2018
contrib Updates Jan 22, 2018
depends base code Jan 16, 2018
dinero-docs Update menu space Mar 6, 2018
doc update ver number Mar 17, 2018
qa Brand update Mar 5, 2018
share Update icons Mar 6, 2018
src Update chainparams.cpp Jun 6, 2018
.gitignore base code Jan 16, 2018
.travis.yml Fix tx number for proper progress perc Feb 11, 2018
CONTRIBUTING.md base code Jan 16, 2018
COPYING base code Jan 16, 2018
INSTALL base code Jan 16, 2018
Makefile.am base code Jan 16, 2018
README.md Brand update Mar 5, 2018
autogen.sh base code Jan 16, 2018
configure.ac Update configure.ac Jun 5, 2018
libdineroconsensus.pc.in base code Jan 16, 2018

README.md

Dinero Core staging tree 1.0.1.0

master: Build Status develop: Build Status

https://www.dinerocoin.org

What is Dinero?

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

License

Dinero 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 Dinero 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 Dinero 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.