iticoin
C++ QMake HTML C Python Assembly Other
Switch branches/tags
Nothing to show
Clone or download
Permalink
Failed to load latest commit information.
MSVC done Jun 19, 2016
contrib done Jun 19, 2016
doc обновления ссылки Mar 19, 2017
share done Jun 19, 2016
src add http://explorer.iticoin.com/ Jul 14, 2017
.gitattributes :octocat: Added .gitattributes & .gitignore files Jun 19, 2016
.gitignore :octocat: Added .gitattributes & .gitignore files Jun 19, 2016
COPYING done Jun 19, 2016
INSTALL done Jun 19, 2016
README done Jun 19, 2016
README.md done Jun 19, 2016
_gitattributes done Jun 19, 2016
_gitignore done Jun 19, 2016
iticoin-qt-android-bdb.pro done Jun 19, 2016
iticoin-qt-mac.pro done Jun 19, 2016
iticoin-qt-windows.pro done Jun 19, 2016
iticoin-qt.pro done Jun 19, 2016

README.md

iTiCoin official development tree

iTiCoin - a hybrid scrypt PoW + PoS based cryptocurrency.

  • 1 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 50000 coins
  • Maximum PoS reward is 0 coins
  • Maximum coins mined 10000000

Development process

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

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