Skip to content
[CRS] Criptoreal - Lyra2z DGWv3 Masternodes Governance
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
build-aux/m4 First Commit - CRS Lyra2z DGW3 Feb 1, 2018
contrib First Commit - CRS Lyra2z DGW3 Feb 1, 2018
depends First Commit - CRS Lyra2z DGW3 Feb 1, 2018
doc Merge branch 'master' of Jun 18, 2018
qa New Themes, Checkpoint and Bump Version Feb 6, 2018
INSTALL First Commit - CRS Lyra2z DGW3 Feb 1, 2018 CRS V1.2.0 Jun 18, 2018

Criptoreal Core 1.1.0

What is Criptoreal?

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


Criptoreal Core is released under the terms of the MIT license. See COPYING for more information or see

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 Criptoreal Core.

The contribution workflow is described in


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/

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.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.