LitecoinDark staging/development tree

Copyright (c) 2009-2014 Bitcoin Developers Copyright (c) 2011-2014 Litecoin Developers Copyright (c) 2014 LitecoinDark Developers (POD-CryptoAsian)

What is LitecoinDark?

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

• 1 minute block targets
• subsidy halves in 12813 blocks
• ~82 million total coins
• 3200 coins per block
• 5 hours retarget difficulty

What is the purpose of this fork?

This cryptocurrency had an impressive hashrate from its original launch as well as a name that seems to pay homage to Bitcoin, Litecoin, Darkcoin, and BitcoinDark. There are some glaring issues with the codebase, along with quite a lot of room for improvements as well as feature additions that could greatly help this blockchain survive and thrive in todays crypty economy.

=======

License

LitecoinDark 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 Litecoin 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 Litecoin.

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
./litecoindark-qt_test