Skip to content
No description, website, or topics provided.
Branch: master
Clone or download
npq7721 updated collateral to be fixed at 20k.
update version to be

add old wallet disconnect at block 206550
Latest commit 63f8639 Jan 15, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.settings initial Aug 7, 2018
autom4te.cache initial Aug 7, 2018
build-aux initial Aug 7, 2018
contrib initial Aug 7, 2018
depends initial Aug 7, 2018
doc initial Aug 7, 2018
qa initial Aug 7, 2018
share initial Aug 7, 2018
snap initial Aug 7, 2018
src updated collateral to be fixed at 20k. Jan 15, 2019
xgalaxy-docs initial Aug 7, 2018
.cproject initial Aug 7, 2018
.gitattributes Source-Code Apr 9, 2018
.gitignore initial Aug 7, 2018
.project initial Aug 7, 2018
.travis.yml initial Aug 7, 2018 initial Aug 7, 2018
COPYING initial Aug 7, 2018
INSTALL initial Aug 7, 2018
LICENSE initial Aug 7, 2018
Makefile initial Aug 7, 2018 initial Aug 7, 2018 initial Aug 7, 2018 Update Aug 19, 2018
aclocal.m4 initial Aug 7, 2018 initial Aug 7, 2018
config.log initial Aug 7, 2018
config.status initial Aug 7, 2018
configure initial Aug 7, 2018 updated collateral to be fixed at 20k. Jan 15, 2019
libbitcoinconsensus.pc iniital Aug 7, 2018 iniital Aug 7, 2018
pkg.m4 Source-Code Apr 9, 2018

xGalaxy Core 1.0.0

What is xGalaxy?

XGalaxy-Coin is a fully decentralised cryptocurrency built on the premise of providing anonymity, speed, fair mining by being ASIC-resistant and reliability by the usage of Masternodes.

For more information, as well as an immediately usable, binary version of the XGalaxy Core software, see


XGalaxy Core is released under the terms of the MIT license. See COPYING for more information or see

Development Process

The master branch is meant to be stable. Development is normally done in separate bran Tags are created to indicate new official,l.0.0 stable release versions of XGalaxy Core.

The contribution workflow is described in


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

There are also regression and integration tests of the RPC interface, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: qa/pull-tester/

The Travis CI system makes sure that every pull request is built for Windows and Linux, OS X, and that unit and sanity tests are automatically run.

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.

You can’t perform that action at this time.