Skip to content
X13 PoW/PoS/Masternode/FastTx/AnonSend Cryptocurrency
C++ C Python CSS M4 Makefile Other
Branch: master
Clone or download

Latest commit

Latest commit ab9f372 Jun 3, 2020

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
build-aux/m4 3.0.x May 2, 2019
contrib Fix Jun 5, 2019
depends fix compile depends Oct 5, 2019
doc remove unnecessary files Jun 6, 2019
docker 3.0.x May 2, 2019
mxt-docs Update README.md May 18, 2020
qa 3.0.x May 2, 2019
share remove unnecessary files Jun 6, 2019
src bump version 4.0.2 Jun 3, 2020
.gitattributes 3.0.x May 2, 2019
.gitignore disconect old versions Jun 6, 2019
CMakeLists.txt 3.0.x May 2, 2019
CONTRIBUTING.md 3.0.x May 2, 2019
COPYING 3.0.x May 2, 2019
INSTALL.md . Apr 22, 2020
Makefile.am 3.0.x May 2, 2019
README.md Update README.md May 19, 2020
autogen.sh 3.0.x May 2, 2019
configure.ac bump version 4.0.2 Jun 3, 2020
libmartexconsensus.pc.in 3.0.x May 2, 2019

README.md

MarteX Core

logo issues forks stars license downloads

What is MarteX?

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

License

MarteX Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

Development Process

The master branch is meant to be stable. Development is normally done in separate branches. Tags are created to indicate new official, stable release versions of MarteX Core.

The contribution workflow is described in CONTRIBUTING.md.

Testing

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/README.md.

There are also regression and integration tests of the RPC interface, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: qa/pull-tester/rpc-tests.py

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.

Documentations

Development documents.

User documents.

You can’t perform that action at this time.