YescryptR32 cryptocurrency
Switch branches/tags
Clone or download
Latest commit 44f61b8 Mar 28, 2018
Permalink
Failed to load latest commit information.
.tx first commit Mar 17, 2018
build-aux/m4 first commit Mar 17, 2018
contrib doc url fix Mar 25, 2018
depends first commit Mar 17, 2018
doc doc url fix Mar 25, 2018
docs B -> V Mar 28, 2018
qa first commit Mar 17, 2018
share first commit Mar 17, 2018
src doc url fix Mar 25, 2018
wabi-docs first commit Mar 17, 2018
.gitattributes first commit Mar 17, 2018
.gitignore first commit Mar 17, 2018
.travis.yml first commit Mar 17, 2018
CONTRIBUTING.md first commit Mar 17, 2018
COPYING first commit Mar 17, 2018
INSTALL first commit Mar 17, 2018
Makefile.am first commit Mar 17, 2018
README.md first commit Mar 17, 2018
autogen.sh first commit Mar 17, 2018
configure.ac MN enforce changed to 2018/04/01 Mar 24, 2018
libwaviconsensus.pc.in first commit Mar 17, 2018

README.md

Wavi Core staging tree 0.12.2

What is Wavi?

Wavi is an experimental new digital currency that enables anonymous, instant payments to anyone, anywhere in the world. Wavi uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Wavi Core is the name of the open source software which enables the use of this currency.

License

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