/peercoin

PPCoin Official Development Tree

Primary LanguageTypeScriptMIT LicenseMIT

Peershares Official Development Repo

What is Peershares?

Peershares are an inexpensive and decentralized ledger to be used by businesses for tracking share ownership and distributing dividends in an automated fashion. Shares can be transferred and held just like other cryptocurrency units, such as peercoins or bitcoins.

Using Peershares, individuals, businesses, or organizations of any size could raise funding through an initial offering without depending on a third party such as a stock exchange. While trading shares through exchanges will be useful to provide liquidity, Peershares can be traded on any number of exchanges just as Peercoins can.

Each business using Peershares will have their own blockchain that is independent of all others. Blockchains can be secured cheaply and easily using Peercoin's proof-of-stake, once the initial (issuer-controlled) shares has been generated using proof-of-work.

Issuers can distribute dividends as Peercoins, which can then be held by the investors, or if they would prefer, can then take those dividends and convert them to another cryptocurrency or fiat through their preferred exchange.

A share issuer is not vulnerable to the failure of single stock exchange such as BTC Trading or Litecoin Global.

Peershares Resources

About Peercoin

Peercoin (abbreviated PPC), also known as PPCoin 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. Peercoin 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.

Peercoin Resources

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