Go to Top

GameCredits Coin (GAME) The currency of GNation

About GameCredits

GameCredits Coin (GAME)

GameCredits Coin (GAME)

One in three humans play video games. It’s a $100B industry. The GameCredits currency and virtual wallet lets gamers and developers buy and sell games and in-game items faster, safer and more privately than with credit cards.



50-99% of all virtual good purchases are fraudulent. GameCredits are based on blockchain. Transactions are permanent. 0% chance of fraud


GAME transactions can be conducted anonymously. You can enjoy your favorite games without having to worry about privacy issues at all.


Credit card transactions take up to 60 days to process. With the GAME Inc. payment system, cash can exchange hands in as little as 60 hours.

GameCredits Core integration/staging tree


What is GameCredits?

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

For more information, as well as an immediately useable, binary version of the GameCredits Core software, see https://gamecredits.org.


GameCredits 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 and tested, but is not guaranteed to be completely stable. Tags are created regularly to indicate new official, stable release versions of GameCredits Core.

The contribution workflow is described in CONTRIBUTING.md.

The mailing list should be used to discuss complicated or controversial changes before working on a patch set.

Developer chat can be found on Discord at #development.


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

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


, , ,

Leave a Reply

Your email address will not be published. Required fields are marked *