Skip to content
View Leprechain's full-sized avatar
🎯
Focusing
🎯
Focusing

Block or report Leprechain

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
Leprechain/README.md

Leprechain Core staging tree 18.0

CI master develop
Gitlab Build Status Build Status

https://www.leprechain.org

For an immediately usable, binary version of the Leprechain Core software, see https://www.leprechain.org/downloads/.

Further information about Leprechain Core is available in the doc folder.

What is Leprechain?

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

For more information read the original Leprechain whitepaper.

License

Leprechain 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 meant to be stable. Development is normally done in separate branches. Tags are created to indicate new official, stable release versions of Leprechain Core.

The contribution workflow is described in CONTRIBUTING.md and useful hints for developers can be found in doc/developer-notes.md.

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

Translations

Changes to translations as well as new translations can be submitted to Leprechain Core's Transifex page.

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.

Popular repositories Loading

  1. Leprechain Leprechain Public

    Leprechain (LPC)

    C++