No description, website, or topics provided.
Switch branches/tags
Nothing to show
Clone or download
Latest commit 5847f45 Nov 17, 2017
Permalink
Failed to load latest commit information.
.tx 0.12.1 Nov 17, 2017
build-aux/m4 0.12.1 Nov 17, 2017
contrib 0.12.1 Nov 17, 2017
dash-docs 0.12.1 Nov 17, 2017
depends 0.12.1 Nov 17, 2017
doc 0.12.1 Nov 17, 2017
qa 0.12.1 Nov 17, 2017
share 0.12.1 Nov 17, 2017
src 0.12.1 Nov 17, 2017
.gitattributes 👾 Added .gitattributes Nov 17, 2017
.travis.yml 0.12.1 Nov 17, 2017
CONTRIBUTING.md 0.12.1 Nov 17, 2017
COPYING 0.12.1 Nov 17, 2017
INSTALL 0.12.1 Nov 17, 2017
Makefile.am 0.12.1 Nov 17, 2017
README.md 0.12.1 Nov 17, 2017
autogen.sh 0.12.1 Nov 17, 2017
configure.ac 0.12.1 Nov 17, 2017
libbitcoinconsensus.pc.in 0.12.1 Nov 17, 2017

README.md

Vivoinnovaonexgobyte Core staging tree 0.12.1

master: Build Status v0.12.0.x: Build Status v0.12.1.x: Build Status

https://www.vivoinnovaonexgobyte.org

What is Vivoinnovaonexgobyte?

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

License

Vivoinnovaonexgobyte 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 Vivoinnovaonexgobyte 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 with: qa/pull-tester/rpc-tests.py

The Travis CI system makes sure that every pull request is built for Windows and Linux, OSX, 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.

Translations

Changes to translations as well as new translations can be submitted to Vivoinnovaonexgobyte Core's Transifex page.

Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.

Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.

Translators should also follow the forum.