No description, website, or topics provided.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
contrib YoCoin Source Oct 20, 2014
doc YoCoin Source Oct 20, 2014
qa/rpc-tests YoCoin Source Oct 20, 2014
share YoCoin Source Oct 20, 2014
src YoCoin Source Oct 20, 2014
.gitattributes YoCoin Source Oct 20, 2014
.gitignore YoCoin Source Oct 20, 2014
COPYING YoCoin Source Oct 20, 2014
INSTALL YoCoin Source Oct 20, 2014
README.md YoCoin Source Oct 20, 2014
yocoin-qt.pro YoCoin Source Oct 20, 2014

README.md

YoCoin (YOC) - a 'faster and better' version of Litecoin which is meant for use by young people as it is very fast.

  • 60 seconds Target Spacing:
  • Coinbase maturity 50 Blocks
  • 200,000,000 total coins
  • no subsidy within the first day and after approximately 10-15 years; in between: 4 coins per generated block
  • difficulty retargets every 4 days
  • currently no block checkpoints are in the code (but could be easily added) Other than that, this coin is exactly like Litecoin.

So actually, this 'new' coin exists for the following to prove that really anyone can start a Litecoin/Bitcoin based currency. (I am 16)

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 official, stable release versions of Litecoin.

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