Paycoin is a Paycoin network-compatible, community-developed wallet client.
The project has been designed to provide people with a stable, secure, and feature-rich alternative to the Paycoin reference wallet (https://github.com/PaycoinFoundation/paycoin).
To help faciliate broad community cooperation, a number of trusted Paycoin/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!
- Source: Source Code
- Documentation: Build Instructions
- Support: Talk Paycoin, Issue Tracker
Paycoin (abbreviated XPY), also known as Paycoin 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. Paycoin is based on Peercoin, 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.
- 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 at Talk Paycoin 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.
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.