Skip to content
🔒 LitecoinZ source tree
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Update Apr 10, 2019
build-aux/m4 [build] Update build-aux Apr 8, 2019
contrib Version 2.0.1 Apr 11, 2019
depends [depends] Add NO_GTEST option Apr 10, 2019
qa Update LitecoinZ URLs Apr 10, 2019
share Update share Apr 10, 2019
src Display download percentage while downloading params files Apr 12, 2019
zcutil [build] Build improvement Apr 8, 2019
.gitattributes Initial commit Nov 30, 2017
.gitignore [build] Build improvement Apr 8, 2019 Update Apr 10, 2019
COPYING Update COPYING Apr 10, 2019 Update Apr 10, 2019 Update share Apr 10, 2019 Update Apr 10, 2019 [build] Build improvement Apr 8, 2019 Version 2.0.1 Apr 11, 2019 [build] Build improvement Apr 8, 2019

LitecoinZ Core integration/staging tree

What is LitecoinZ?

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

LitecoinZ is an implementation of the "Zerocash" protocol forked from ZCash. Based on Bitcoin's code, it intends to offer a far higher standard of privacy through a sophisticated zero-knowledge proving scheme that preserves confidentiality of transaction metadata.

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


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

The Travis CI system makes sure that every pull request is built for Windows, Linux, and macOS, 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 LitecoinZ 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.


Donations for supporting developers are welcome:

  • LTC: LgSbGGqru5LVHE3cWcgwZDLjr3WorGahr3
  • BTC: 1N2rQimKbeUQA8N2LU5vGopYQJmZsBM2d6
  • ZEC: t1T8hAYzLNwe2rLQpFMjx9z9FHFd6oQ86P9
  • BTG: GNkwW2uS4ed7cofz94J8PrTXJnZgmk5nr2
  • BTCZ: t1cmr2QUMCEBRhUVrZHsgC6DnrdzC2FyHz7


You can’t perform that action at this time.