Skip to content
No description, website, or topics provided.
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
build-aux/m4 Initial commit Mar 28, 2018
contrib Fork to 2.0 Apr 30, 2019
depends Fork to 2.0 Apr 30, 2019
doc Fork to 2.0 Apr 30, 2019
qa Initial commit Mar 28, 2018
share Fork to 2.0 Apr 30, 2019
src Fork to 2.0 Apr 30, 2019
whitepapers Uploaded TRVC 2.0 Whitepaper to GitHub May 7, 2019
.gitignore Fork to 2.0 Apr 30, 2019
.travis.yml Initial commit Mar 28, 2018
CONTRIBUTING.md Fork to 2.0 Apr 30, 2019
COPYING Fork to 2.0 Apr 30, 2019
INSTALL Fork to 2.0 Apr 30, 2019
LICENSE Initial commit Feb 21, 2018
Makefile.am Fork to 2.0 Apr 30, 2019
README.md Fork to 2.0 Apr 30, 2019
autogen.sh Initial commit Mar 28, 2018
configure.ac Fork to 2.0 Apr 30, 2019
libtrivechainconsensus.pc.in Fork to 2.0 Apr 30, 2019

README.md

Trivechain

https://trivechain.com

What is Trivechain?

Trivechain is a public blockchain managed by Decentralized autonomous organization (DAO) with focus on bridging businesses to enter the new era digital age with implementation of blockchain-based technology and DApps (decentralized applications)

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.

You can’t perform that action at this time.