Switch branches/tags
Nothing to show
Clone or download
MasterMold MasterMold2MasterCar
1 checkpoint
+ rebranding
Latest commit 3c2447d Jul 20, 2015

What is MasterCar ?

MasterCar is a Litecoin [LTC] based scryptcoin. Dedicated to buy physical collectors [BIG CARS MINIATURES 1/8th scale] The choice of the product will be driven by the community.

Currency name: MasterCar Abbreviation: MCAR Quantity: 2991837 Algorithm: sCrypt Mining period: approx. 10 years Block Maturity : 10 blocks Block time : 30 secondes Block reward : from O.7 to 40 Difficulty Retarget : every 5 blocks Premine : 2,58703933402789%

Info for MasterCar:

For more information, as well as an immediately useable, binary version of the MasterCar client sofware, see

MasterCar integration/staging tree

Copyright (c) 2009-2015 Bitcoin Developers Copyright (c) 2015 MasterCar Developers


MasterCar is released under the terms of the MIT license. See COPYING for more information or see

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


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
make -f Makefile.test