No description, website, or topics provided.
TypeScript C++ C Prolog Python Objective-C
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
doc
share
src
.gitattributes
.gitignore
COPYING
INSTALL
Makefile.Debug
Makefile.Release
README
README.md
object_script.richcoin-qt.Debug
object_script.richcoin-qt.Release
richcoin-qt.pro

README.md

Richcoin - a new crypto coin focus on increase your wealth. Like Litecoin it uses scrypt as a proof of work scheme.

    - Total coins will be 88,888,888.
    - 88 seconds per block 
	- 88 coins per block, will be halved every 508 days (or 4,993,68 blocks)
		- 1-588 blocks: 0 coins
		- 589-688 blocks: 8 coins
		- 689-788 blocks: 18 coins
		- 789-888 blocks: 28 coins
		- 889-988 blocks: 38 coins
		- 989-1888 blocks: 58 coins
		- 1889-2888 blocks: 68 coins
		- from 2889 block, the reward is 88 coins.
		
    - Difficulty retargets once every 88 blocks
	- 3 confirmations per transaction.
    - Ports: connection 28888, RPC 58888.

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