Subi Core Staging Repo
Branch: master
Clone or download
Latest commit a5b995e Feb 1, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github SubiCore Dec 19, 2018
.tx SubiCore Dec 19, 2018
build-aux/m4 SubiCore Dec 19, 2018
contrib SubiCore Dec 19, 2018
depends Update Depends Dec 27, 2018
doc SubiCore Dec 19, 2018
images SubiCore Dec 19, 2018
scripts Version Feb 1, 2019
share Permissions Dec 19, 2018
src Version Feb 1, 2019
test SubiCore Dec 19, 2018
.gitattributes SubiCore Dec 19, 2018
.gitignore Bump boost Jan 8, 2019
.travis.yml SubiCore Dec 19, 2018 SubiCore Dec 19, 2018
COPYING SubiCore Dec 19, 2018 SubiCore Dec 19, 2018
LICENSE SubiCore Dec 19, 2018 SubiCore Dec 19, 2018 Update Readme Jan 27, 2019 Permissions Dec 19, 2018 Version Feb 1, 2019 SubiCore Dec 19, 2018


Build Status Discord serverfollow on Twitter

WebsiteSubiDesktopBlock ExplorerDiscordForumTelegramTwitter


  • Initial PoW Distribution
  • Hybrid SubiNode System
  • Hybrid PoS/SubiNode (After Initial Distribution)
  • Segwit
  • Smart Contracts
  • Shade Technology

Subi Specifications

Specification Value
Algorithm Neoscrypt / X16R - after block 60,000
Developer Fund 5%
Initial PoW Blocks 150,000
PoS Start Block 150,000
Block Size 4MB
Block Time 60s
PoW Reward 45 SUBI / 2.5 SUBI (after block 60,000)
PoS Reward 5% reducing each year
Stake Time 24 hours
SubiNode Requirement 10,000 SUBI
SubiNode Reward 30% PoW/PoS
Port 5335
RPC Port 5336
SubiNode Port 5335

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

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/

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 try to prompt our users for the basic information We always need for new issues. Please fill out the issue template below and submit it to our discord channel. ISSUE_TEMPLATE