Skip to content
Hatch - Reinventing Cryptocurrency
C++ C Python CSS M4 Makefile Other
Branch: master
Clone or download
Pull request Compare This branch is 6 commits ahead of dashpay:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Rename Sep 5, 2019
.tx Rename Sep 5, 2019
build-aux/m4 Rename Sep 5, 2019
ci Rename Sep 5, 2019
contrib Rename Sep 5, 2019
depends Rename Sep 5, 2019
doc Rename Sep 5, 2019
docker Rename Sep 5, 2019
qa Rename Sep 5, 2019
share Update logo Sep 14, 2019
src Update BIP44 Sep 14, 2019
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.gitignore Rename Sep 5, 2019
.travis.yml Rename Sep 5, 2019
CMakeLists.txt Rename Sep 5, 2019
COPYING Rename Sep 5, 2019 Rename Sep 5, 2019
Jenkinsfile Rename Sep 5, 2019
Jenkinsfile.gitian Rename Sep 5, 2019 Rename Sep 5, 2019 Merge bitcoin#8784: Copyright headers for build scripts Jan 12, 2018 Rename Sep 5, 2019 Rename Sep 5, 2019

Hatch Core staging tree 0.14.0

master: Build Status develop: Build Status

What is Hatch?

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

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


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

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

The contribution workflow is described in


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 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/

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.


Changes to translations as well as new translations can be submitted to Hatch Core's Transifex page.

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.

Translators should also follow the forum.

You can’t perform that action at this time.