A next generation cryptocurrency
Switch branches/tags
Nothing to show
Clone or download
Latest commit 0ef4183 Nov 6, 2017
Permalink
Failed to load latest commit information.
build Initial commit Oct 2, 2017
contrib Initial commit Oct 2, 2017
doc Initial commit Oct 2, 2017
share Initial commit Oct 2, 2017
src Initial commit Oct 2, 2017
.DS_Store Initial commit Oct 2, 2017
.gitattributes Initial commit Oct 2, 2017
.gitignore Initial commit Oct 2, 2017
COPYING Initial commit Oct 2, 2017
INSTALL Initial commit Oct 2, 2017
LICENSE Initial commit Oct 2, 2017
Makefile Initial commit Oct 2, 2017
README Initial commit Oct 2, 2017
README.md Update README.md Nov 6, 2017
SBCcoin-qt.pro Initial commit Oct 2, 2017

README.md

sbccoin-source

SBCCoin - a hybrid scrypt PoW + PoS based cryptocurrency.

10 minutes stake spacing 30 minutes PoW spacing Balanced PoW blocks and stakes weighting The PoW subsidy halves every x64 multiply of PoW difficulty The PoS interest halves every x64 multiply of PoS difficulty Maximum PoW reward is 50 coins Maximum PoS reward is 100 coins No deterministic limit of the supply,

Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.

The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if they don't match the project's coding conventions (see coding.txt) or are controversial.

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are regularly created to indicate new official, stable release versions of SBCCoin.

Feature branches are created when there are major new features being worked on by several people.

From time to time a pull request will become outdated. If this occurs, and the pull is no longer automatically mergeable; a comment on the pull will be used to issue a warning of closure. The pull will be closed 15 days after the warning if action is not taken by the author. Pull requests closed in this manner will have their corresponding issue labeled 'stagnant'.

Issues with no commits will be given a similar warning, and closed after 15 days from their last activity. Issues closed in this manner will be labeled 'stale'.