Skip to content
Forking Test without TrapDoor Algorithm
Branch: master
Clone or download
Pull request Compare This branch is 214 commits ahead, 3431 commits behind litecoin-project:master.
Latest commit 3233b09 Apr 9, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Update Apr 5, 2018
build-aux/m4 Minor changes for 0.15 (litecoin-project#445) Feb 27, 2018
contrib Create wixlar Apr 5, 2018
doc Minor changes for 0.15 (litecoin-project#445) Feb 27, 2018
share Litecoin: Branding Jan 19, 2018
src Minor changes for 0.15 (litecoin-project#445) Feb 27, 2018
.gitattributes Update .gitattributes Apr 9, 2018
.gitignore Litecoin: Branding Jan 19, 2018
.travis.yml Litecoin: Update Travis Jan 19, 2018
COPYING Litecoin: Adjust license year range to 2018 Jan 19, 2018 Minor changes for 0.15 (litecoin-project#445) Feb 27, 2018 Update Apr 5, 2018 Add MIT license to and share/ Sep 21, 2016

Wixlarcoin Core integration/staging tree

Build Status

What is WixlarCoin?

Wixlar is a Global Decentralized Digital Currency based on the BlockChain Technology which is instant, secure, private and with low fee transactions. With Wixlar coins, you can buy and sell products or services online and offline. Wixlar Group offers some of the latest advanced technological services through a Global Decentralized Network.

Wixlar TV: Wixlar TV Channel broadcasting live 24/7 with the latest news in business and technology. Streaming Live internationally at


Wixlarcoin 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]( /wixlarcoin/tags) are created regularly to indicate new official, stable release versions of Wixlarcoin Core.

The contribution workflow is described in

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


We only accept translation fixes that are submitted through Bitcoin Core's Transifex page. Translations are converted to Wixlarcoin 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.

You can’t perform that action at this time.