Skip to content
No description, website, or topics provided.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.tx new commit Nov 14, 2017
build-aux/m4 new commit Nov 14, 2017
contrib new commit Nov 14, 2017
dash-docs new Nov 14, 2017
depends new Nov 14, 2017
doc new commit Nov 14, 2017
qa new commit Nov 14, 2017
share new commit Nov 14, 2017
src Update pow.cpp Feb 22, 2018
zozocoin-docs new commit Nov 14, 2017
.gitattributes new Nov 14, 2017
.gitignore new commit Nov 14, 2017
.travis.yml new commit Nov 14, 2017
CONTRIBUTING.md new commit Nov 14, 2017
COPYING new commit Nov 14, 2017
INSTALL new commit Nov 14, 2017
Makefile new commit Nov 14, 2017
Makefile.am new commit Nov 14, 2017
README.md new Nov 14, 2017
autogen.sh initial commit Oct 17, 2017
configure.ac new commit Nov 14, 2017
libbitcoinconsensus.pc.in new Nov 14, 2017
rename.sh ZOZO to ZZC Oct 19, 2017

README.md

Zozo Core staging tree 0.12.1

master:

What is Zozo?

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

License

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

You can’t perform that action at this time.