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.
Go to file
David Burkett cd1660afaf
Updating release notes
3 weeks ago
.github Litecoin: Branding 3 years ago
.tx tx: Update transifex slug for 0.21 4 years ago
build-aux/m4 Litecoin: Build system and utilties 3 years ago
build_msvc v0.21.3: update version, release notes and manpages 1 month ago
ci fix: secp-zkp refs + VG_CHECK test + block_assemble bench 2 months ago
contrib Adding additional peers 3 weeks ago
depends build: use -isysroot over --sysroot on macOS 2 months ago
doc Updating release notes 3 weeks ago
share build: set minimum supported macOS to 10.14 2 years ago
src Adding additional peers 3 weeks ago
test disable unfinshed test & fix missing ismweb from testfiles 2 months ago
.appveyor.yml Update vcpkg checkout commit. 3 years ago
.cirrus.yml build: set minimum supported macOS to 10.14 2 years ago
.fuzzbuzz.yml ci: Add fuzzbuzz integration 4 years ago
.gitattributes Separate protocol versioning from clientversion 10 years ago
.gitignore build: Run libdmg-hfsplus's DMG tool in make deploy 2 years ago
.python-version .python-version: Specify full version 3.5.6 5 years ago
.style.yapf test: .style.yapf: Set column_limit=160 5 years ago
.travis.yml ci: Run windows ci config on cirrus 3 years ago
CODEOWNERS doc: Add comments and additional reviewers to CODEOWNERS file 4 years ago Litecoin: Branding 3 years ago
COPYING Litecoin: Bump copyright year 3 years ago Litecoin: Branding 3 years ago build: Replace genisoimage with xorriso 2 years ago Litecoin: Update 3 years ago Litecoin: Security doc 3 years ago scripted-diff: Bump copyright of files changed in 2019 4 years ago Bumping version to v0.21.3 3 weeks ago build: remove libcrypto as internal dependency in libbitcoinconsensus.pc 4 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 (see doc/build-*.md for instructions) and tested, but it is not guaranteed to be completely stable. Tags are created regularly from release branches to indicate new official, stable release versions of Litecoin Core.

The repository is used exclusively for the development of the GUI. Its master branch is identical in all monotree repositories. Release branches and tags do not exist, so please do not fork that repository unless it is for development reasons.

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.