No description, website, or topics provided.
TypeScript C++ C Python IDL Objective-C
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
bitcoin-qt.pro

README.md

Blesscoin integration/staging tree

http://www.blesscoin.org

Copyright (c) 2009-2013 Bitcoin Developers

Copyright (c) 2011-2013 Litecoin Developers

Copyright (c) 2013-2015 Blesscoin Developers

What is Blesscoin?

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

  • 1 minute block targets
  • subsidy halves in 1000k blocks (~2 years)
  • ~100 million total coins
  • 1440 blocks to retarget difficulty ( 1 day)
  • 60 confirms for mining on network

The rest is the same as Bitcoin.

  • 50 coins per block

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

License

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

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