GINcoin Core is the official wallet of the GINcoin cryptocurrency
Branch: master
Clone or download
Pull request Compare This branch is 138 commits ahead, 1686 commits behind dashpay:master.
Latest commit 0c9eece Feb 17, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
build-aux/m4 v1.0.0.0 Feb 23, 2018
contrib version bump Feb 10, 2019
depends gitian build fixex and outdated dependencies fiexes Feb 7, 2019
doc added ubuntu16 docker build script and instructions Jan 21, 2019
gincoin-docs v1.0.0.0 Feb 23, 2018
qa Dpow (#2) Feb 3, 2019
share DGW parameters change + checkpoints - v1.0.2.0 Apr 4, 2018
src Fix St13runtime_error Feb 17, 2019
.gitattributes v1.0.0.0 Feb 23, 2018
.gitignore v1.0.0.0 Feb 23, 2018 v1.0.0.0 Feb 23, 2018
COPYING v1.0.0.0 Feb 23, 2018
INSTALL v1.0.0.0 Feb 23, 2018 gitian build fixex and outdated dependencies fiexes Feb 7, 2019 updated readme Feb 3, 2019 v1.0.0.0 Feb 23, 2018 version bump Feb 10, 2019
libgincoinconsensus.pc Dpow (#2) Feb 3, 2019 v1.0.0.0 Feb 23, 2018

Gincoin Core staging tree 1.2.0


Gincoin 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 branches. Tags are created to indicate new official, stable release versions of Gincoin 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/

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.