Sprouts Official Development Tree
Pull request Compare This branch is 9 commits ahead of sproutcoin:master.
JacksonBriggs update apr
changed from 1000% to 100% per month.

Latest commit 19a0ab4 Oct 13, 2015
Failed to load latest commit information.
contrib StrongHands Sep 27, 2015
doc update ports Sep 27, 2015
share StrongHands Sep 27, 2015
src update apr Oct 13, 2015
.gitattributes Build identification strings Apr 10, 2012
.gitignore StrongHands Sep 27, 2015
COPYING StrongHands Sep 27, 2015
INSTALL Update build instructions for the new, no-wxwidgets world Sep 26, 2011
README.md StrongHands Sep 27, 2015
sprouts.pro StrongHands Sep 27, 2015


StrongHands Official Development Repository

What is StrongHands?

StrongHands is a StrongHands network-compatible, community-developed wallet client.

The project has been designed to provide people with a stable, secure, and feature-rich alternative to the StrongHands reference wallet (http://github.com/ppcoin/ppcoin).

To help faciliate broad community cooperation, a number of trusted StrongHands/Peershares community leaders have write permissions to the project's codebase, allowing for decentralization and continuity. Community members, old and new, are encouraged to find ways to contribute to the success of the project. If you have experience with programming, product design, QA engineering, translation, or have a different set of skills that you want to bring to the project, your involvement is appreciated!

StrongHands Resources

About StrongHands

StrongHands (abbreviated SHND), also known as StrongHands and Peer-to-Peer Coin is the first cryptocurrency design introducing proof-of-stake consensus as a security model, with a combined proof-of-stake/proof-of-work minting system. StrongHands is based on Bitcoin, while introducing many important innovations to cryptocurrency field including new security model, energy efficiency, better minting model and more adaptive response to rapid change in network computation power.

Repo Guidelines

  • Developers work in their own forks, then submit pull requests when they think their feature or bug fix is ready.
  • If it is a simple/trivial/non-controversial change, then one of the development team members simply pulls it.
  • If it is a more complicated or potentially controversial change, then the change may be discussed in the pull request, or the requester may be asked to start a discussion StrongHands Talk for a broader community discussion.
  • 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.
  • 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. Pull requests closed in this manner will have their corresponding issue labeled 'stagnant'.
  • For development ideas and help see here.

Translation Guidelines

Changes to translations as well as new translations can be submitted to StrongHands's Get Localization page.

Translations are periodically pulled from Get Localization and merged into the git repository.

Important: We do not accept translation changes as GitHub pull requests because the next pull from Get Localization would automatically overwrite them again.