No description, website, or topics provided.
C++ Python HTML C OpenEdge ABL Roff Other
Switch branches/tags
Nothing to show
Latest commit 4146949 Oct 30, 2017 @rupeedigitalassets rupeedigitalassets Update Sourcecode
Sourcecode Updated
Permalink
Failed to load latest commit information.
contrib first commit Mar 28, 2017
doc Source Code Updated Oct 11, 2017
qa/rpc-tests first commit Mar 28, 2017
share first commit Mar 28, 2017
src Update Sourcecode Oct 30, 2017
.gitattributes first commit Mar 28, 2017
.gitignore first commit Mar 28, 2017
COPYING first commit Mar 28, 2017
INSTALL first commit Mar 28, 2017
README.md Update Source Code Oct 11, 2017
RUPEE-qt.pro Update Source Code Oct 11, 2017

README.md

RUPEE integration/staging tree

https://rupeeblockchain.org

Copyright © 2009-2017 Bitcoin Developers Copyright © 2011-2016 The Litecoin Core Developers Copyright © 2017 RUPEE Developers

What is RUPEE?

RUPEE is a lite version of Bitcoin using scrypt as a proof-of-work algorithm.

  • 2.5 minute block targets
  • subsidy halves in 640k blocks (~3 years)
  • ~84 million total coins
  • 50 coins per block

License

RUPEE is released under the terms of the MIT license. See COPYING for more information or see http://opensource.org/licenses/MIT.

Development process

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 RUPEE 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 with the devs and community.

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

The 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 RUPEE.

Testing

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.

Automated Testing

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 RUPEE-qt.pro
make -f Makefile.test
./rupee-qt_test