Litecoin Core integration/staging tree
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Adrian Gallagher fa0cdba24a
Merge pull request #650 from MiWCryptoCurrency/qpainterpath_fix
7 months ago
.github Litecoin: More branding 2 years ago
.travis Litecoin: Add scrypt support to Travis 2 years ago
.tx qt: Pre-0.18 split-off translations update 3 years ago
build-aux/m4 Litecoin: Branding 2 years ago
build_msvc Litecoin: More branding 2 years ago
contrib Litecoin: Bump copyright year 2 years ago
depends Litecoin: Branding 2 years ago
doc Litecoin: 0.18.1 release notes 2 years ago
share Litecoin: Branding 2 years ago
src Add missing QPainterPath include 2 years ago
test Litecoin: Adjust fee system 2 years ago
.appveyor.yml Litecoin: Branding 2 years ago
.gitattributes Separate protocol versioning from clientversion 7 years ago
.gitignore Litecoin: Branding 2 years ago
.python-version .python-version: Bump to 3.5.6 3 years ago
.travis.yml Litecoin: Add scrypt support to Travis 2 years ago Litecoin: Branding 2 years ago
COPYING Litecoin: Bump copyright year 2 years ago Litecoin: Branding 2 years ago Litecoin: Branding 2 years ago Litecoin: Update 2 years ago Add "export LC_ALL=C" to all shell scripts 4 years ago Litecoin: Bump copyright year 2 years ago Unify package name to as few places as possible without major changes 6 years ago

Litecoin Core integration/staging tree

Build Status

What is Litecoin?

Litecoin is an experimental digital currency that enables instant payments to anyone, anywhere in the world. Litecoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Litecoin 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 Litecoin Core software, see


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

The contribution workflow is described in and useful hints for developers can be found in doc/

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 #litecoin-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 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 Litecoin 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.