No description, website, or topics provided.
Switch branches/tags
Nothing to show
Clone or download
Latest commit 675b03d Jul 10, 2018
Permalink
Failed to load latest commit information.
build-aux/m4 initial commit Jun 19, 2018
contrib initial commit Jun 19, 2018
depends initial commit Jun 19, 2018
doc initial commit Jun 19, 2018
qa initial commit Jun 19, 2018
share initial commit Jun 19, 2018
src Update default.css Jul 10, 2018
CONTRIBUTING.md initial commit Jun 19, 2018
COPYING initial commit Jun 19, 2018
INSTALL initial commit Jun 19, 2018
Makefile.am initial commit Jun 19, 2018
README.md Update README.md Jul 10, 2018
autogen.sh initial commit Jun 19, 2018
configure.ac Update configure.ac Jul 10, 2018
pkg.m4 initial commit Jun 19, 2018

README.md

Vivid Core 1.0.0.2

VividCoin is a custom Blockchain, backed by Masternodes, designed to give the Vivid Platform ultra fast and near zero cost transactions for it's rewards system and beyond.

Links:

License

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