Project of Mindexcoin Blockchain.
Branch: 0.16
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Litecoin: Branding Mar 15, 2018
build-aux/m4 Initial commit Jan 21, 2019
contrib Initial commit Jan 21, 2019
doc Initial commit Jan 21, 2019
share Initial commit Jan 21, 2019
src Initial commit Jan 21, 2019
test Initial commit Jan 21, 2019
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.gitignore Litecoin: Branding Mar 15, 2018
.travis.yml Initial commit Jan 21, 2019 Initial commit Jan 21, 2019
COPYING Initial commit Jan 21, 2019 Initial commit Jan 21, 2019 Initial commit Jan 21, 2019 Initial commit Jan 21, 2019 Add MIT license to and share/ Sep 21, 2016 Initial commit Jan 21, 2019 Unify package name to as few places as possible without major changes Dec 14, 2015
mindexcoin.conf Initial commit Jan 21, 2019

Mindexcoin Core integration/staging tree

Build Status

What is Mindexcoin?

Mindexcoin is an experimental digital currency that enables instant payments to anyone, anywhere in the world. Mindexcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Mindexcoin Core is the name of open source software which enables the use of this currency.

For more information, as well as an immediately useable, binary version of the Mindexcoin Core software, see


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

Development Process

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 Mindexcoin Core.

The contribution workflow is described in

The developer mailing list should be used to discuss complicated or controversial changes before working on a patch set.

Developer IRC can be found on Freenode at #mindexcoin-dev.


Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, 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 can be compiled and run (assuming they weren't disabled in configure) with: make check. Further details on running and extending unit tests can be found in /src/test/

There are also regression and integration tests, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: test/functional/

The Travis CI system makes sure that every pull request is built for Windows, Linux, and OS X, and that unit/sanity tests are run automatically.

Manual Quality Assurance (QA) Testing

Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.


We only accept translation fixes that are submitted through Bitcoin Core's Transifex page. Translations are converted to Mindexcoin periodically.

Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.

Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.