No description, website, or topics provided.
C++ TypeScript Assembly HTML C Python Other
Switch branches/tags
Nothing to show
Clone or download
Latest commit d0a8983 Sep 7, 2016
Permalink
Failed to load latest commit information.
MSVC FedoraShare Sep 7, 2016
contrib FedoraShare Sep 7, 2016
doc FedoraShare Sep 7, 2016
share FedoraShare Sep 7, 2016
src FedoraShare Sep 7, 2016
.gitattributes 🍭 Added .gitattributes & .gitignore files Sep 7, 2016
COPYING FedoraShare Sep 7, 2016
INSTALL FedoraShare Sep 7, 2016
LICENSE FedoraShare Sep 7, 2016
README FedoraShare Sep 7, 2016
README.md FedoraShare Sep 7, 2016
fedorashare.pro FedoraShare Sep 7, 2016

README.md

FedoraShare Official Development Tree

http://www.fedorashare.org

Copyright (c) 2009-2016 Bitcoin Developers
Copyright (c) 2011-2016 LiteCoin Developers
Copyright (c) 2016 FedoraShare Developers

FedoraShare - a hybrid scrypt PoW + PoS based cryptocurrency, using scrypt as a proof-of-work algorithm.

RPC port is 26668, P2P port is 26666

5 minutes Stake spacing
5 minutes PoW spacing
Balanced PoW blocks and stakes weighting
PoW reward is 0 coins
PoS reward has flat reward of 20 coins.
Total of 500,000,000,000 coins.
Currently ~ 499000035969 coins mined

For more information, as well as an immediately useable, binary version of the FedoraShare client software, see http://www.fedorashare.org.

License

FedoraShare is released under the terms of the MIT license. See COPYING for more information or see http://opensource.org/licenses/MIT.

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

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