Skip to content
v2.1.2 New QuantisNet Core Blockchain - Ready for Release 6-3-2019
Branch: master
Clone or download
Latest commit 8ea1929 Jun 14, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
build-aux/m4 Add Mainnet Code Jun 3, 2019
contrib update git descriptors links Jun 13, 2019
dash-docs Add Mainnet Code Jun 3, 2019
depends Add Mainnet Code Jun 3, 2019
doc [Trivial] Update Git and website links in compiles Jun 13, 2019
qa Add Mainnet Code Jun 3, 2019
quantisnet-docs Add Mainnet Code Jun 3, 2019
share BITCOIN to QUANTISNET Jun 13, 2019
src [Trivial] Update Git and website links in compiles Jun 13, 2019
.DS_Store Add Mainnet Code Jun 3, 2019
.travis.yml
CONTRIBUTING.md Add Mainnet Code Jun 3, 2019
COPYING Add Mainnet Code Jun 3, 2019
INSTALL.md Add Mainnet Code Jun 3, 2019
LICENSE Add Mainnet Code Jun 3, 2019
Makefile.am BITCOIN to QUANTISNET Jun 13, 2019
README.md Add Mainnet Code Jun 3, 2019
Vagrantfile Add Mainnet Code Jun 3, 2019
autogen.sh add Jun 14, 2019
configure.ac BITCOIN to QUANTISNET Jun 13, 2019
futoin.json disable test compiles Jun 14, 2019
libquantisnetconsensus.pc.in Add Mainnet Code Jun 3, 2019

README.md

QuantisNet Core

https://www.QuantisNetwork.org/

What is QuantisNet?

For more information, as well as an immediately useable, binary version of the QuantisNet Core software, see https://www.QuantisNetwork.org/ .

License

QuantisNet 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 QuantisNet 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. Further details on running and extending unit tests can be found in /src/test/README.md.

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, Linux, and OS X, and that unit/sanity tests are run automatically.

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.