Binaries and source code for HTH, Help The Homeless Coin
Switch branches/tags
Nothing to show
Clone or download
Altcoin-Cash Revert "Add bip39"
This reverts commit 6f72718.
Latest commit 7fe4023 Nov 16, 2018
Failed to load latest commit information.
.settings refractor proton to change proton references to reden Apr 10, 2018
autom4te.cache latest Jul 15, 2018
build-aux refac Jun 21, 2018
contrib fix files Jul 1, 2018
depends refac Jun 21, 2018
doc Merge pull request #7 from Altcoin-Cash/patch-4 Oct 17, 2018
hth-docs collateral change Sep 13, 2018
qa fix files Jul 1, 2018
res fix files Jul 1, 2018
share fix files Jul 1, 2018
snap fix files Jul 1, 2018
src Revert "Add bip39" Nov 16, 2018
.cproject refac Jun 21, 2018
.gitattributes Source-Code Apr 9, 2018
.gitignore refac Jun 21, 2018
.project refac Jun 21, 2018
.travis.yml refac Jun 21, 2018 refac Jun 21, 2018
COPYING refac Jun 21, 2018
INSTALL refac Jun 21, 2018
LICENSE refac Jun 21, 2018
Light_Paper.pdf HTH light paper Oct 4, 2018 refac Jun 21, 2018 fix files Jul 1, 2018 Added logo Sep 15, 2018
about.png added hth image Sep 13, 2018
aclocal.m4 fix files Jul 1, 2018 refac Jun 21, 2018
configure Merge branch 'master' into master Sep 19, 2018 Merge branch 'master' into master Sep 19, 2018 Source-Code Apr 9, 2018
pkg.m4 Source-Code Apr 9, 2018
res.rar fix files Jul 1, 2018

HTH Core

What is HTH?

HTH-Coin is a fully decentralised cryptocurrency built on the premise of providing anonymity, speed, fair mining by being ASIC-resistant and reliability by the usage of Masternodes.

For more information see or discord:

An immediately usable, binary version of the HTH Core software is available at


HTH 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 bran Tags are created to indicate new official, stable release versions of HTH 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

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 and Linux, OS X, and that unit and sanity tests are automatically run.

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.