No description, website, or topics provided.
TypeScript C++ C Python IDL Objective-C
Switch branches/tags
Nothing to show
Clone or download
Pull request Compare This branch is 25 commits ahead of maxpwr:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
contrib Luckycoin client v1.0.1 Apr 10, 2014
doc
share luckycoin May 24, 2013
src
.gitattributes
.gitignore luckycoin May 24, 2013
COPYING
INSTALL Documentation update Nov 17, 2013
README
README.md Luckycoin client v1.0.1 Apr 10, 2014
luckycoin-qt.pro Luckycoin client v1.0.1 Apr 10, 2014

README.md

Luckycoin Client v1.0.1

Luckycoin - a fork of Litecoin version with random bonus blocks. Like Litecoin it uses scrypt as a proof of work scheme.

  • 1 min block target
  • Difficulty retargets every 20 min with accelerated diff adjustment in the beginning
  • Initially 88 coins per block, halves every 2 months (100,000 blocks)
  • Total around 20 millions coins
  • connection port is 9917, RPC-port 9918

Random Super-blocks: For the 1st 50000 blocks (1st month) - 5% chances 188 coins/block - 1% chances 588 coins/block - 0.01% chances 5888 coins/block (so expect 5 such blocks)

After 50000 blocks
- 5% chances 2 times the normal coins (i.e. if normal is 88 coins, you get 176 coins)
- 1% chances 5 times the normal coins
- 0.01% chance 58 times the normal coins

Official Luckycoin Website and Community Forum

Please visit the official Luckycoin website and community forum for more information. http://luckycoin.cc https://cryptocointalk.com/forum/188-luckycoin-lky/

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