Ringo integration/staging tree
Copyright (c) 2009-2014 Bitcoin Developers
Copyright (c) 2011-2012 PPCoin Developers
Copyright (c) 2013 NovaCoin Developers
Copyright (c) 2014 Blackcoin Developers
Copyright (c) 2014-2018 Ringo Developers
What is Ringo?
Ringo is a lite version of Bitcoin using Scrypt as a PoW & PoS algorithm.
For more information, as well as an immediately useable, binary version of the Ringo client sofware, see https://github.com/dkwzjw/ringo.
Ringo is released under the terms of the MIT license. See
COPYING for more
information or see http://opensource.org/licenses/MIT.
Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.
If it is a simple/trivial/non-controversial change, then one of the Ringo development team members simply pulls it.
If it is a more complicated or potentially controversial change, then the patch submitter will be asked to start a discussion (if they haven't already) on the mailing list.
The patch will be accepted if there is broad consensus that it is a good thing.
Developers should expect to rework and resubmit patches if the code doesn't
match the project's coding conventions (see
doc/coding.txt) or are
master branch is regularly built and tested, but is not guaranteed to be
completely stable. Tags are created
regularly to indicate new official, stable release versions of Ringo.
Testing and code review is the bottleneck for development; we get more pull requests than we can review and test. Please be patient and help out, and remember this is a security-critical project where any mistake might cost people lots of money.
Developers are strongly encouraged to write unit tests for new code, and to submit new unit tests for old code.
Unit tests for the core code are in
src/test/. To compile and run them:
cd src; make -f makefile.unix test
Unit tests for the GUI code are in
src/qt/test/. To compile and run them:
qmake BITCOIN_QT_TEST=1 -o Makefile.test ringo-qt.pro make -f Makefile.test ./ringo-qt_test