Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

INNOVATIVE and DECENTRALIZED crypto currency that have the bases (fast, secure and anonymous transactions, low fees) to become the best digital payment asset for buying/selling goods and service around the world. NYX will also be the starting point around which we will create a complex system of tools and services for ecommerce, trading and crypto world.

Anonymized transactions using coin mixing technology. 1-Second-Transactions. Network stability with masternodes, each is secured with a collateral of 1.000 NYX.

For further information visit us at

Coin Specs

• PoW Algorithm: NeoScrypt
• Premine: (#1 Block) 1,000,000 NYX • Type: POW + Masternode • Block Time: 120 Seconds
• PoW Max Coin Output/Supply: 30,350,000 • Masternode Requirements: 1,000 NYX
• Maturity: 101 Confirmations

Block Reward Distribution

Blocks Reward Reward Distribution
Minner Masternode
1 - 64800 10 NYX 20% 80%
64801 - 129600 15 NYX 30% 70%
129601 - 262800 20 NYX 40% 60%
262801 - 525600 10 NYX 40% 60%
after 525601 -10% / year* 40% 60%
*) Starting with block 525601 the reward will decrease by 10% every year


NYX 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 Vivo 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