Scrypt PoW cryptocurrency
Switch branches/tags
Nothing to show
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
contrib Update copyright Oct 12, 2018
doc Update assets-attribution.txt Oct 12, 2018
share grandcoin Jul 13, 2013
src Add files via upload Oct 12, 2018
.gitattributes grandcoin Jul 13, 2013
.gitignore grandcoin Jul 13, 2013
COPYING grandcoin Jul 13, 2013
INSTALL grandcoin Jul 13, 2013
README grandcoin Jul 13, 2013 Update Oct 12, 2018 Removed GrandcoinMiner Oct 14, 2018

Grandcoin - a decendent of Litecoin that combines the great features from Luckycoin (random blocks) and Florincoin (transaction message). Like Litecoin it uses scrypt as a proof of work scheme.

- 45 seconds block time
- Difficulty retargets every 30 blocks 
- Expected total coins will be 1,427,621,642.
- 6 confirmations for transaction
- 50 confirmations for minted blocks
- Low transaction fees.
- Every day (on average) there is a random superblock with 5000-10000 coins.
- Every week (on average) (7 days) there is a random super+ block with 50000-100000 coins.
- The prize will be halved every year.
- First 3 days are bonus days with 5x, 3x, and 2x the normal prizes.

- The default ports are 12377(Connect) and 12378(RPC).

The official website is:

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