No description, website, or topics provided.
Switch branches/tags
Nothing to show
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
build-aux Initial Jan 21, 2018
contrib Fix gitian RPi dependency Feb 6, 2018
depends Initial Jan 21, 2018
doc Initial Jan 21, 2018
qa Initial Jan 21, 2018
share Initial Jan 21, 2018
src Build version; Folder naming fix Feb 6, 2018
stonecoin-docs Initial Jan 21, 2018
.gitattributes Initial Jan 21, 2018 Initial Jan 21, 2018
COPYING Initial Jan 21, 2018
INSTALL Initial Jan 21, 2018 Initial Jan 21, 2018 Initial Jan 21, 2018 Initial Jan 21, 2018
aclocal.m4 Initial Jan 21, 2018 Initial Jan 21, 2018
configure Build version; Folder naming fix Feb 6, 2018 Build version; Folder naming fix Feb 6, 2018 Initial Jan 21, 2018

StoneCoin Core staging tree

What is StoneCoin?

StoneCoin (STONE) is an innovative cryptocurrency. A form of digital currency secured by cryptography and issued through a decentralized and advanced mining market. Based on Dash, it's an enhanced and further developed version, featuring the masternode technology, near-instant and secure payments as well as anonymous transactions. StoneCoin has great potential for rapid growth and expansion. Based on a total Proof of Work and Masternode system, it is accesible to everyone, it ensures a fair and stable return of investment for the Graphics Processing Units (GPUs) miners and the Masternode holders.

Additional information, wallets, specifications & roadmap:


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