Skip to content

IrishCoinProject/IrishCoin

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

89 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Irishcoin integration/staging tree

http://www.IrishCoin.org

Copyright (c) 2011 Litecoin Developers

Copyright (c) 2014 Maplecoin Developers

Copyright (c) 2014 Irishcoin Developers

What is Irishcoin?

Irishcoin is a fork of MapleCoin using scrypt as a proof-of-work algorithm.

  • 2 minute block targets
  • subsidy halves in 320k blocks (~1.5 year)
  • ~64 million total coins
  • 100 coins per block
  • 4 blocks to retarget difficulty

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

License

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

Releases

No releases published

Packages

No packages published

Languages

  • TypeScript 66.7%
  • C++ 31.3%
  • C 1.2%
  • Python 0.5%
  • IDL 0.2%
  • Objective-C++ 0.1%