Nucleon Blockchain
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.
.github rebrand Oct 5, 2018
.tx rebrand Oct 5, 2018
build-aux/m4 removed webview Oct 23, 2018
contrib Revert "Update" Feb 20, 2019
depends Update Nov 8, 2018
doc masternodes validation Oct 13, 2018
docker rebrand Oct 5, 2018
neon-docs rebrand Oct 5, 2018
qa rebrand Oct 5, 2018
share fee + gui update Nov 2, 2018
src Revert "when new block hits 16 mins, it pays 10% of regular reward" Feb 20, 2019
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.gitignore rebrand Oct 5, 2018
.travis.yml Revert "Update .travis.yml" Feb 20, 2019
CMakeLists.txt rebrand Oct 5, 2018 rebrand Oct 5, 2018
COPYING Update COPYING Dec 14, 2018 rebrand Oct 5, 2018 rebrand Oct 5, 2018 Update Dec 20, 2018 Merge #8784: Copyright headers for build scripts Jan 12, 2018 Fixed versioning in Dec 20, 2018
libneonconsensus.pc rebrand Oct 5, 2018

Nucleon Core staging tree 2.2.0

master: Build Status develop: Build Status

What is Nucleon?

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

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


Nucleon 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 Nucleon 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. Further details on running and extending unit tests can be found in /src/test/

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


Changes to translations as well as new translations can be submitted to Nucleon Core's Transifex page.

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.