CompuCoin Source Code
TypeScript C++ C Python IDL Shell Other
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
contrib
doc
share
src
COPYING
INSTALL
README.md
compucoin-qt.pro

README.md

CompuCoin integration/staging tree

http://www.compucoin.org admin@compucoin.org

Copyright (c) 2009-2013 Bitcoin Developers Copyright (c) 2011-2013 Litecoin Developers Copyright (c) 2014 CompuCoin Developers

What is CompuCoin?

CompuCoin is a version of Litecoin using scrypt as a proof-of-work algorithm.

CompuCoin | Ticker: CPN Algorithm: Scrypt Max Coins: 35 Million CPN Company Stock: 8 Million CPN (23%) Block Time: 120 Seconds
Difficulty: Retarget Kimoto’s gravity well every day Block Halving Rate: 1,802,057 Blocks Block Award: 8 CPN


For more information, as well as an immediately useable, binary version of the CompuCoin client sofware, see http://www.compucoin.org

License

CompuCoin 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 CompuCoin 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 appropriate channels.

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. regularly to indicate new official, stable release versions of CompuCoin.

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