Skip to content

LabyrinthCore/Labyrinth

Repository files navigation

Labyrinth Core integration/staging tree

https://labyrinthcore.com

What is Labyrinth?

Labyrinth Core (LAB) is an open-source, Bitcoin-derived digital currency that serves as the core of our escrow service. Labyrinth Escrow is a platform where multiple parties can transact with each other, under predefined conditions, without the need for trust. This is possible due to conditions being set and executed similarly to smart contracts. The entire transaction validation happens on the chain, rendering the usual escrow attacks impractical.

License

Labyrinth 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 (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 Labyrinth 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, 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

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.