Fork coins, for the TARTARIA project
Switch branches/tags
Nothing to show
Clone or download
Latest commit 9a0cda1 Jul 28, 2018
Failed to load latest commit information.
contrib 1 Jul 15, 2018
doc 1 Jul 15, 2018
share 1 Jul 15, 2018
src Delete cecece Jul 15, 2018
.gitattributes 1 Jul 15, 2018
.gitignore Add files via upload Jul 15, 2018
COPYING 1 Jul 15, 2018 1 Jul 15, 2018
INSTALL Update INSTALL Jul 28, 2018
README 1 Jul 15, 2018 Update Jul 28, 2018

If your wallet can not independently find public nodes for synchronization of the blockchain, add the following lines to the configuration file GRIF.conf: addnode = addnode = addnode = addnode =

GRIF development tree

GRIF is a PoS-based cryptocurrency.

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 stable release versions of GRIF.

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