This repository has been archived by the owner. It is now read-only.
No description, website, or topics provided.
Clone or download
Latest commit 451e1e6 Dec 24, 2017
Failed to load latest commit information.
contrib Initial Commit Feb 28, 2017
doc Initial Commit Feb 28, 2017
share Update Mac bundle identifier for codesigning Apr 10, 2017
src Archive Dec 24, 2017
.gitattributes Initial Commit Feb 28, 2017
.gitignore Initial Commit Feb 28, 2017
COPYING Initial Commit Feb 28, 2017
INSTALL Initial Commit Feb 28, 2017
README Initial Commit Feb 28, 2017 Archive Dec 24, 2017 Increment Version Aug 29, 2017

ARCHIVED REPOSITORY - Do not use for building Pinkcoin.

This repository has been archived. The project has moved to:

Please use that repository from now on.


Pinkcoin development tree

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

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