Skip to content

pixelfairies/link

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

6 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Pixels (♥) - a 'faster' version of Litecoin which also uses scrypt as a proof of work scheme and is intended for microtransactions.

  • 30 seconds block targets: beat that MinCoin! ;)
  • 1 Trillion + 1 Million total coins
  • no subsidy within the first 20 blocks in between: 1000 coins per generated block
  • difficulty retargets every hour
  • currently peers are looked up over IRC only
  • currently no block checkpoints are in the code (but could be easily added)

Other than that, this coin is exactly like Litecoin and should by no means be used as a real cryptocurrency only a poser coin. All of the coin parameters are chosen precicely with 'fairness' towards everyone in mind.

So actually, this 'new' coin exists for the following reasons:

  • ♥'s proves that really anyone(!) can start a Litecoin/Bitcoin based currency (just look at the changes I applied to the original Litecoin source, for genesis block generation look at main.cpp)
  • allows me to experiment with coin parameters (in a private network)

This coin was cloned in 48 hours time..

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