No description, website, or topics provided.
Switch branches/tags
Clone or download
terrence-c Merge pull request #4 from jsheng08/patch-1
Update Masternode Setup Guide
Latest commit f55486b Sep 3, 2018
Permalink
Failed to load latest commit information.
build-aux/m4 Initial commit Mar 28, 2018
contrib Initial commit Mar 28, 2018
depends Initial commit Mar 28, 2018
doc Update masternode-setup.md Sep 3, 2018
qa Initial commit Mar 28, 2018
share - Update consensus, allow ASIC mining. Apr 11, 2018
src Bump to 1.3.0.1 Aug 10, 2018
.gitignore Initial commit Mar 28, 2018
.travis.yml Initial commit Mar 28, 2018
CONTRIBUTING.md Initial commit Mar 28, 2018
COPYING Initial commit Mar 28, 2018
INSTALL Initial commit Mar 28, 2018
LICENSE Initial commit Feb 21, 2018
Makefile.am Initial commit Mar 28, 2018
README.md Update README.md Apr 2, 2018
autogen.sh Initial commit Mar 28, 2018
configure.ac Bump to 1.3.0.1 Aug 10, 2018
libtrivecoinconsensus.pc.in Initial commit Mar 28, 2018

README.md

Trivechain

https://www.trivecoin.org

What is Trivechain?

Trivechain is a crypto-currency based on Bitcoin, with various improvements such as a two-tier incentivized network, known as the TRIVE VIP Masternode(TVIP) network. Included are other improvements such as ExclusiveSend(ES), for increasing fungibility and DirectSend(DS) which allows instant transaction confirmation without a centralized authority. Trivecoin specially build for commercial purpose hybrid coin.

License

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

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.