Skip to content
RACE - your cryptocurrency of the future
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
contrib Initial Import Jan 31, 2018
doc Initial Import Jan 31, 2018
race-docs Initial Import Jan 31, 2018
share Initial Import Jan 31, 2018
src Initial Import Jan 31, 2018
.gitattributes Initial Import Jan 31, 2018
.gitignore add missing depends patches Jan 31, 2018
.travis.yml Update .travis.yml Feb 22, 2018
COPYING Initial Import Jan 31, 2018
INSTALL Initial Import Jan 31, 2018 Initial Import Jan 31, 2018 Initial Import Jan 31, 2018 Initial Import Jan 31, 2018 Update Apr 28, 2019

Race Core staging tree 0.12.2 | Block Explorer | Announcement | Discord | Twitter

About Race

RACE offers highly secured, anonymous transactions across the world. RACE supports Masternodes with a good and constant block reward. Features as Private Send and Instant Send make RACE a future-oriented currency on the market. RACE uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Race Core is the name of the open source software which enables the use of this currency. Race Core is based on the newest Dash codebase and is its own currency.

For more information, as well as an immediately useable, binary version of the Race Core software, see

Race Specifications

Specification Value
PoW Algorithm Lyra2REv2
Block Time Average 90 seconds
Block Reward 8 RACE
Block Reward Distribution 40% to Masternodes, 60% to Miners initially, ramping up to 65% Masternodes, 35% miners
Masternode Collateral 1000 RACE
Estimated Supply 32.7 Mio.
Difficulty Retargeting Every block
Difficulty Algorithm Dark Gravity Wave v3


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