Skip to content
Main release & integration tree for Litecoin Cash
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Email addresses and URLs fixed May 25, 2018
.tx tx: Update transifex slug for 0.16 Jan 24, 2018
build-aux/m4 Initial rebranding May 24, 2018
contrib Fixed gitian descriptors Dec 19, 2018
depends
doc
share Gfx refreshed, Hive page added, spacedrop badge added, seeds updated Jul 12, 2018
src Merge branch 'master' of https://github.com/litecoincash-project/lite… Feb 20, 2019
test Initial rebranding May 24, 2018
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.gitignore
.travis.yml Initial rebranding May 24, 2018
CONTRIBUTING.md
COPYING Copyrights updated, GI renamed Feb 2, 2019
INSTALL.md
Makefile.am
README.md Update README.md Jul 19, 2018
autogen.sh
configure.ac Bumped version number Feb 6, 2019
libbitcoinconsensus.pc.in Unify package name to as few places as possible without major changes Dec 14, 2015

README.md

Litecoin Cash Core integration/staging tree

What is Litecoin Cash?

Litecoin Cash is a SHA256 fork of Litecoin. For full details, as well as prebuilt binaries for Windows, Mac and Linux, please visit our website at https://litecoinca.sh.

Litecoin Cash Core is the full node software that makes up the backbone of the LCC network.

License

Litecoin Cash Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

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

The contribution workflow is described in CONTRIBUTING.md.

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 #litecoincash-dev.

Testing

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/README.md.

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/test_runner.py

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.

Translations

Any translation corrections or expansions are welcomed as GitHub pull requests.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.