C++ Python C HTML QMake Makefile Other
Clone or download
Latest commit 86796cd Mar 25, 2018
Failed to load latest commit information.
Releases Same as v1.4 version Mar 25, 2018
contrib fix patch for osx Oct 7, 2017
doc s/lite,bit/marscoin Feb 7, 2014
share any fix Feb 24, 2014
src fix for new osx Oct 7, 2017
.gitattributes Build identification strings Apr 10, 2012
.gitignore fixed default rpc port for testnet Jun 17, 2014
COPYING s/lite,bit/marscoin Feb 7, 2014
INSTALL s/lite,bit/marscoin Feb 7, 2014
README.md readme update Jan 2, 2018
marscoin-qt.pro fix for new osx Oct 7, 2017


Marscoin integration/staging tree



Copyright (c) 2009-2013 Bitcoin Developers

Copyright (c) 2011-2013 Litecoin Developers

Copyright (c) 2013-2018 Marscoin Developers

What is Marscoin?

Marscoin targets to become the blockchain for Mars, and functions as a proof of concept for incentivizing and privatizing space exploration funding.

  • scrypt Litecoin-based cryptocurrency
  • DarkGravityWave network protection
  • confirmation block every 2 Mars minutes (123 seconds)
  • subsidy halves every Mars year (668 sols)
  • 721 blocks per sol
  • 12.5 coins per block
  • 48 million total coins by 2024
  • 500k donation for non-profit MarsOne
  • 500k donation for The Mars Society
  • developed and supported by The Marscoin Foundation, LLC (a non-profit).

For more information, as well as an immediately useable, binary version of the Marscoin client sofware, see http://www.marscoin.org and http://www.marscoinfoundation.org


Marscoin 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 Marscoin 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).

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


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 MARSCOIN_QT_TEST=1 -o Makefile.test marscoin-qt.pro
make -f Makefile.test


alt tag