PURA – the world’s first socially and environmentally conscious cryptocurrency. Desktop client and node
Branch: master
Clone or download
puracore Update README.md
Latest commit 5728db7 Sep 24, 2017
Type Name Latest commit message Commit time
Failed to load latest commit information.
.tx Initial Upload Sep 24, 2017
build-aux/m4 Initial Upload Sep 24, 2017
contrib Initial Upload Sep 24, 2017
depends Initial Upload Sep 24, 2017
doc Initial Upload Sep 24, 2017
pura-docs Initial Upload Sep 24, 2017
qa Initial Upload Sep 24, 2017
share Initial Upload Sep 24, 2017
src Initial Upload Sep 24, 2017
.gitattributes Initial Upload Sep 24, 2017
.gitignore Initial Upload Sep 24, 2017
.travis.yml Initial Upload Sep 24, 2017
CONTRIBUTING.md Initial Upload Sep 24, 2017
COPYING Initial Upload Sep 24, 2017
INSTALL Initial Upload Sep 24, 2017
Makefile.am Initial Upload Sep 24, 2017
README.md Update README.md Sep 24, 2017
autogen.sh Initial Upload Sep 24, 2017
configure.ac Initial Upload Sep 24, 2017
libpuraconsensus.pc.in Initial Upload Sep 24, 2017


Pura Core staging tree 1.0.0


What is Pura ?

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


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

The contribution workflow is described in CONTRIBUTING.md.


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.


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