Clone or download
Failed to load latest commit information.
autom4te.cache X16R Jul 3, 2018
build-aux X16R Jul 3, 2018
contrib UI fixes/redesign (credits ACP) Jul 24, 2018
depends X16R Jul 3, 2018
doc fix broken repo link Oct 6, 2018
qa X16R Jul 3, 2018
share GUI update, param adjustment Nov 3, 2018
sov-docs X16R Jul 3, 2018
src GUI update, param adjustment Nov 3, 2018
.DS_Store Update secp256k1 folder Jul 22, 2018
.gitattributes Initial commit Jul 3, 2018
.gitignore Initial commit Jul 3, 2018 X16R Jul 3, 2018
COPYING X16R Jul 3, 2018
INSTALL X16R Jul 3, 2018
LICENSE Initial commit Jul 3, 2018 X16R Jul 3, 2018 X16R Jul 3, 2018 GUI update, param adjustment Nov 3, 2018
aclocal.m4 X16R Jul 3, 2018 X16R Jul 3, 2018
configure X16R Jul 3, 2018 GUI update, param adjustment Nov 3, 2018
deploy_rsa.enc X16R Jul 3, 2018 X16R Jul 3, 2018
orchid222.png X16R Jul 3, 2018
radio_checked.png X16R Jul 3, 2018
static.png X16R Jul 3, 2018

SOV Core 2.0.1

What is SOV?

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


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