Skip to content
No description, website, or topics provided.
C++ C Python CSS M4 Makefile Other
Branch: master
Clone or download
Latest commit 86454a0 Sep 6, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github
.tx Initial commit Jul 3, 2019
build-aux/m4 Initial commit Jul 3, 2019
ci full sourcetree update to v0.13.x Sep 5, 2019
contrib full sourcetree update to v0.13.x Sep 5, 2019
depends full sourcetree update to v0.13.x Sep 5, 2019
doc full sourcetree update to v0.13.x Sep 5, 2019
docker Initial commit Jul 3, 2019
nachocoin-docs Initial commit Jul 3, 2019
qa full sourcetree update to v0.13.x Sep 5, 2019
share full sourcetree update to v0.13.x Sep 5, 2019
src barry repair Sep 5, 2019
.gitattributes Initial commit Jul 3, 2019
.gitignore full sourcetree update to v0.13.x Sep 5, 2019
.travis.yml full sourcetree update to v0.13.x Sep 5, 2019
CMakeLists.txt full sourcetree update to v0.13.x Sep 5, 2019
CONTRIBUTING.md full sourcetree update to v0.13.x Sep 5, 2019
COPYING
INSTALL.md Initial commit Jul 3, 2019
Jenkinsfile full sourcetree update to v0.13.x Sep 5, 2019
Jenkinsfile.gitian full sourcetree update to v0.13.x Sep 5, 2019
Makefile.am Initial commit Jul 3, 2019
README.md
autogen.sh source reapirs and file permissions Jul 29, 2019
configure.ac full sourcetree update to v0.13.x Sep 5, 2019
libnachocoinconsensus.pc.in Initial commit Jul 3, 2019

README.md

Nacho Core staging tree 0.13

master: [![Build Status]

What is Nacho?

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

License

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

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.